Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Claude Code: Add Claude Code rules, commands, and authoring skill

Open
#200 1 comment 0 reactions 1 assignee View on GitHub

@Ayush8923 is already working on this.

Since Jul 21, 2026.

  • #201 by @vprashrex — open

Assessment

This issue has not been assessed yet.

Description

enhancement

Is your feature request related to a problem?
AI-assisted contributions to kaapi-frontend lack codified conventions, leading to inconsistent code and repetitive review feedback. There's also no standard process for verification, issue creation, or PR drafting, which complicates development.

Describe the solution you'd like
Add a .claude/ toolset to define repo conventions and workflows:

  • Rules (.claude/rules/): seven auto-loaded convention files for structure and quality.
  • new-feature skill (.claude/skills/new-feature/SKILL.md): a 7-step authoring process with guidelines.
  • Commands (.claude/commands/): include commands for linting, issue creation, and PR drafting.
Original issue

Is your feature request related to a problem?
AI-assisted contributions to kaapi-frontend currently have no codified conventions — each session re-derives component structure, hook patterns, API proxy style, and quality limits from scratch, producing inconsistent code and repeated review feedback. There is also no standard workflow for verification, issue creation, or PR drafting.

Describe the solution you'd like
Add a .claude/ toolset that encodes the repo's conventions and workflows:

  • Rules (.claude/rules/): seven auto-loaded convention files — components.md, hooks.md, api-and-data-fetching.md, styling.md, types-and-constants.md, utils.md, code-quality.md (500 LOC limit, complexity caps, file-splitting seams).
  • new-feature skill (.claude/skills/new-feature/SKILL.md): 7-step authoring contract — branch, orient via rules, reuse-first scan, correct placement, in-style writing, limits, lint+build verification.
  • Commands (.claude/commands/): /check (drive lint + production build to green), /create-issue (templated feature/enhancement issues), /create-pr (Issue link + Summary PR format), plus a pr-review update.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
19h 4m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProjectTech4DevAI/kaapi-frontend

All issues in ProjectTech4DevAI/kaapi-frontend

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.