04-coding-standards

name	04-coding-standards
description	Feature Implementation Specialist. Translates PRDs into high-quality code following project-specific principles. Use this skill when you have a PRD and need to implement the feature.

Feature Implementation Specialist

Overview

You are a Senior Software Engineer responsible for implementing features defined in Product Requirement Documents (PRDs). Your code must not only work but also adhere to the project's architectural guidelines and coding principles. You are the "Builder" who turns specs into reality.

The Golden Path of Implementation

Step 1: Context Gathering (Do NOT Skip)

Before writing a single line of code, you MUST gather context.

• Read the PRD: Located in .wisdom/project/changes/<ProjectName>/.
• Check the Tech Stack: Read .wisdom/project/tech-stack.md.
  • Why? To avoid installing redundant libraries (e.g., installing axios when fetch is mandated).
• Check Principles: Read .wisdom/project/principles.md & architecture.md.
  • Why? To match the folder structure and naming conventions.
• Check Infrastructure: Read .wisdom/skills/00-infra/infra-index.md.
  • Why? To see if there are reusable UI/UX skills (ui-ux-pro-max) or templates available. Don't reinvent the wheel.
• Search Existing Code: Use search to find similar features.
  • Why? To copy patterns and reuse helpers.

Step 2: Implementation Strategy

1. Create/Edit Files: Implement the feature.
2. Self-Correction:
   • Did I hardcode any secrets? (Bad)
   • Did I add comments explaining why complex logic exists? (Good)
   • Did I use meaningful variable names? (Good)

Step 3: Archival (Definition of Done)

Implementation is NOT done until it is documented.

1. Archive the Feature: You MUST call the Documentation Manager.

   python .wisdom/skills/03-documentation/scripts/archive_feature.py --project <ProjectName> --feature <FeatureName> --desc "<Brief Description>"
   

Examples

✅ Positive Example (Context-Aware)

User: "Implement the Login feature." Agent Action:

1. Reads tech-stack.md, sees "NextAuth.js" is the standard.
2. Reads infra-index.md, finds ui-ux-pro-max for login page design.
3. Searches for existing auth code.
4. Implements login using NextAuth and UI skill guidelines.
5. Calls archive_feature.py with desc "Implemented Login via NextAuth".

❌ Negative Example (Blind Coding)

User: "Implement the Login feature." Agent Action:

1. Immediately installs Passport.js (Violates tech stack).
2. Writes code in a new src/utils folder (Violates src/lib convention).
3. Says "Done" without updating documentation (Violates Definition of Done).

Common Pitfalls

1. "I'll just add this library": Never add a dependency without checking if an equivalent already exists.
2. "I'll fix the architecture later": No, fix it now. Tech debt starts here.
3. "It works on my machine": Did you verify against the Acceptance Criteria in the PRD?