phase-2-convention
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Skill for defining coding rules and conventions. Ensures consistent code style and specifies coding standards.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
- ww-w-ai/bkit-codextheir own version, first seen Feb 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-codex★ 69same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- output-style-setupSkill
- pdcaSkill
- phase-1-schemaSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- skill-statusSkill
- starterSkill
- zero-script-qaSkill
The file
Files
Phase 2: Convention Definition
Establish coding standards and conventions
Categories
1. Naming Conventions
| Type | Convention | Example |
| Components | PascalCase | UserProfile.tsx |
| Functions | camelCase | getUserById() |
| Constants | UPPER_SNAKE | MAX_RETRY_COUNT |
| Files | kebab-case | user-service.ts |
| CSS Classes | kebab-case | user-card |
2. File Structure
src/
├── components/ # UI components
├── hooks/ # Custom hooks
├── lib/ # Utilities
├── services/ # API services
├── types/ # TypeScript types
└── utils/ # Helper functions3. Git Conventions
feat: Add user login
fix: Resolve password reset bug
docs: Update README
style: Format code
refactor: Extract auth service
test: Add login tests
chore: Update dependencies4. Code Style
- Max line length: 100
- Indentation: 2 spaces
- Quotes: Single quotes
- Semicolons: Required
- Trailing commas: ES5
Output
Save to: docs/01-plan/conventions.md
Next Phase
After completion: /phase-3-mockup
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.