@compilr-dev/agents-coding 0.1.1 → 0.2.0

package/dist/skills/index.d.ts

@@ -29,6 +29,16 @@ export declare const projectOnboardingSkill: Skill;
  * Code optimization skill
  */
 export declare const codeOptimizationSkill: Skill;
+/**
+ * Build skill - Implement a backlog item end-to-end
+ * Moved from @compilr-dev/agents because it uses run_tests, run_lint
+ */
+export declare const buildSkill: Skill;
+/**
+ * Scaffold skill - Create project foundation based on tech stack
+ * Moved from @compilr-dev/agents because it uses detect_project
+ */
+export declare const scaffoldSkill: Skill;
 /**
  * All coding skills
  */

package/dist/skills/index.js

@@ -305,6 +305,195 @@ export const codeOptimizationSkill = defineSkill({
     tags: ['performance', 'optimization', 'workflow'],
     version: '1.0.0',
 });
+/**
+ * Build skill - Implement a backlog item end-to-end
+ * Moved from @compilr-dev/agents because it uses run_tests, run_lint
+ */
+export const buildSkill = defineSkill({
+    name: 'build',
+    description: 'Implement a backlog item end-to-end',
+    tags: ['implementation', 'coding'],
+    prompt: `You are in BUILD MODE. Implement the specified backlog item.
+
+## ITEM TO IMPLEMENT
+- **ID:** {{item_id}}
+- **Title:** {{item_title}}
+- **Type:** {{item_type}}
+- **Priority:** {{item_priority}}
+- **Description:** {{item_description}}
+
+## BEFORE STARTING
+
+1. Show the item details to the user in a clear format
+2. Use ask_user_simple to confirm: "Proceed with implementation?"
+   - Options: "Yes, let's build it", "No, pick a different item", "Cancel"
+3. If there are dependency warnings, mention them and ask if user wants to proceed anyway
+
+## CONTEXT TO READ
+
+Before implementing, read these files for context:
+- **PRD.md** (if exists): Project vision and requirements
+- **CLAUDE.md**: Coding standards and conventions
+- **Existing code**: Understand patterns already in use
+
+## IMPLEMENTATION WORKFLOW
+
+### Phase 1: Plan
+1. Use todo_write to create implementation checklist:
+   - Break down the item into concrete tasks
+   - Identify files to create or modify
+   - Note any edge cases to handle
+2. Update backlog status to 🚧 using backlog_write
+
+### Phase 2: Implement
+1. Write code following project conventions from CLAUDE.md
+2. Add tests if the project has a test framework
+3. Keep changes focused on the backlog item scope
+4. Use todo_write to track progress through tasks
+
+### Phase 3: Verify
+1. Run tests with run_tests tool
+2. Run lint with run_lint tool
+3. If tests or lint fail:
+   - Analyze the error message
+   - Fix the issue
+   - Re-run verification
+   - Repeat up to 3 times
+4. If still failing after 3 attempts:
+   - Report the issue to user
+   - Keep status as 🚧
+   - Ask for guidance
+
+### Phase 4: Complete
+1. Update backlog status to ✅ using backlog_write
+2. Create git commit with message format:
+   - feat({{item_id}}): {{item_title}} - for features
+   - fix({{item_id}}): {{item_title}} - for bugs
+   - chore({{item_id}}): {{item_title}} - for chores
+3. Update backlog with the commit SHA
+4. Clear todos with todo_write
+5. Summarize what was implemented
+
+## RULES
+
+- Follow coding standards from CLAUDE.md strictly
+- Keep commits atomic - one backlog item per commit
+- Ask user via ask_user_simple if you hit blockers
+- Don't over-engineer - implement exactly what the item describes
+- Don't add features beyond what was requested
+- Use todo_write throughout to show progress
+- Always run tests before marking complete`,
+    version: '1.0.0',
+});
+/**
+ * Scaffold skill - Create project foundation based on tech stack
+ * Moved from @compilr-dev/agents because it uses detect_project
+ */
+export const scaffoldSkill = defineSkill({
+    name: 'scaffold',
+    description: 'Create project foundation based on tech stack',
+    tags: ['setup', 'foundation', 'scaffolding'],
+    prompt: `You are creating the PROJECT SCAFFOLD (foundation).
+
+## PURPOSE
+
+Create the base project structure that features will be built on top of.
+This is the skeleton that makes feature implementation possible.
+
+## CONTEXT TO READ
+
+First, read these files to understand what to build:
+- **CLAUDE.md**: Tech stack, coding standards, project type
+- **PRD.md** (if exists): Project vision and requirements
+- **Existing files**: What already exists (if anything)
+
+## BEFORE STARTING
+
+1. Summarize the detected/specified tech stack
+2. Use ask_user_simple to confirm: "Create project scaffold with this stack?"
+   - Options: "Yes, create it", "No, let me specify", "Cancel"
+3. If user wants to specify, ask about tech stack preferences
+
+## SCAFFOLD BY PROJECT TYPE
+
+### Web Application (React/Vue/Svelte)
+
+Create:
+- \`src/\` folder structure:
+  - \`src/components/\` - Reusable components
+  - \`src/pages/\` or \`src/routes/\` - Page components
+  - \`src/lib/\` or \`src/utils/\` - Utility functions
+  - \`src/styles/\` - Global styles
+- \`package.json\` with dependencies
+- Build config (\`vite.config.ts\`, \`next.config.js\`, etc.)
+- \`index.html\` entry point (if applicable)
+- Basic App component with routing setup
+- CSS/Tailwind configuration
+- \`.gitignore\`
+- \`README.md\` with setup instructions
+
+### API / Backend (Node/Python/Go)
+
+Create:
+- \`src/\` folder structure:
+  - \`src/routes/\` or \`src/api/\` - API endpoints
+  - \`src/services/\` - Business logic
+  - \`src/models/\` - Data models
+  - \`src/utils/\` - Utilities
+- \`package.json\` / \`requirements.txt\` / \`go.mod\`
+- Entry point (\`src/index.ts\`, \`main.py\`, \`main.go\`)
+- Basic server setup (Express, FastAPI, Gin, etc.)
+- Health check endpoint (\`GET /health\`)
+- Environment config (\`.env.example\`)
+- \`.gitignore\`
+- \`README.md\` with setup instructions
+
+### CLI Tool (Node/Python/Rust)
+
+Create:
+- \`src/\` folder structure:
+  - \`src/commands/\` - Command handlers
+  - \`src/utils/\` - Utilities
+- \`package.json\` with \`bin\` entry / \`setup.py\` / \`Cargo.toml\`
+- Entry point with argument parsing
+- Basic command structure (help, version)
+- \`.gitignore\`
+- \`README.md\` with usage instructions
+
+### Full-Stack Application
+
+Create both frontend and backend structures:
+- \`frontend/\` or \`client/\` - Web app scaffold
+- \`backend/\` or \`server/\` - API scaffold
+- Root \`package.json\` with workspace config (if monorepo)
+- \`docker-compose.yml\` (optional)
+- \`.gitignore\`
+- \`README.md\` with setup instructions
+
+## POST-SCAFFOLD STEPS
+
+1. Install dependencies:
+   - \`npm install\` / \`pip install -r requirements.txt\` / etc.
+2. Run build to verify:
+   - \`npm run build\` / equivalent
+3. Run lint to verify:
+   - \`npm run lint\` / equivalent
+4. Create initial git commit:
+   - \`chore: initial project scaffold\`
+5. Update backlog:
+   - Mark scaffold CHORE as ✅ (if exists)
+
+## RULES
+
+- Follow conventions from CLAUDE.md
+- Use modern, widely-adopted patterns
+- Keep it minimal - only what's needed to start
+- Don't add features - just structure
+- Ensure the project builds and lints clean
+- Add helpful comments in config files
+- Include TypeScript/type hints where applicable`,
+    version: '1.0.0',
+});
 /**
  * All coding skills
  */
@@ -315,6 +504,8 @@ export const codingSkills = [
     prWorkflowSkill,
     projectOnboardingSkill,
     codeOptimizationSkill,
+    buildSkill,
+    scaffoldSkill,
 ];
 /**
  * Export individual skills for selective use

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/agents-coding",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "description": "Coding-specific tools for @compilr-dev/agents - Git, project detection, smart runners, and code search",
   "type": "module",
   "main": "dist/index.js",
@@ -71,11 +71,11 @@
     "node": ">=18.0.0"
   },
   "peerDependencies": {
-    "@compilr-dev/agents": "^0.2.0"
+    "@compilr-dev/agents": "^0.3.0"
   },
   "devDependencies": {
     "@anthropic-ai/sdk": "^0.30.1",
-    "@compilr-dev/agents": "^0.2.0",
+    "@compilr-dev/agents": "^0.3.0",
     "@eslint/js": "^9.39.1",
     "@types/node": "^24.10.1",
     "@vitest/coverage-v8": "^3.2.4",