Capstone - Designing a Team Kiro Setup

.kiro/
├── steering/
│   ├── conventions.md              # Always-on: team-wide code standards
│   ├── architecture.md             # Always-on: project structure, key decisions
│   ├── component-patterns.md       # fileMatch: "src/app/**/*.component.ts"
│   ├── service-patterns.md         # fileMatch: "src/app/**/*.service.ts"
│   ├── testing-standards.md        # fileMatch: "**/*.spec.ts"
│   ├── api-layer.md                # fileMatch: "src/app/services/api/**"
│   └── deployment-guide.md         # Manual: only when deploying
│
├── hooks/
│   ├── lint-on-save.json           # PostFileSave: run ng lint on .ts/.html
│   ├── test-after-task.json        # PostTaskExec: run affected tests
│   └── protect-prod-config.json    # PreToolUse: gate writes to environment.prod.ts
│
├── skills/
│   ├── commit-message.md           # Generate commit messages from diff
│   ├── pr-review.md                # Review PR against team standards
│   └── new-feature.md              # Scaffold a new feature module
│
├── agents/
│   └── researcher.md               # Read-only exploration agent
│
├── settings/
│   └── mcp.json                    # MCP servers (project-specific only)
│
└── specs/
    ├── auth--user-login/
    ├── commerce--order-management/
    └── ...

---
inclusion: auto
---

# Team Conventions
- Angular 18 with standalone components
- State management: Angular signals (not NgRx for new code)
- HTTP: HttpClient with typed responses, catchError in services
- Styling: SCSS with design tokens from @company/tokens
- Testing: Jest with Testing Library, property-based tests for business logic
- Package manager: pnpm
- Commit format: [branch-name] Short title\n\n- Details

---
inclusion: fileMatch
fileMatchPattern: "src/app/**/*.component.ts"
---

# Component Patterns
- Always standalone (no NgModules)
- Use inject() not constructor injection
- Use signals for local state
- OnPush change detection for all components
- Template: inline for <20 lines, separate file otherwise
- Prefer computed() over manual derivation

---
inclusion: manual
---

# Deployment Guide
Refer to deployment procedures in #[[file:docs/deployment/runbook.md]]
...

{
  "version": "v1",
  "hooks": [{
    "name": "Lint on Save",
    "trigger": "PostFileSave",
    "matcher": "\\.(ts|html)$",
    "action": { "type": "command", "command": "bash -c 'FILE=$(cat | jq -r .filePath); npx ng lint --files \"$FILE\"'" }
  }]
}

{
  "version": "v1",
  "hooks": [{
    "name": "Run Tests After Task",
    "trigger": "PostTaskExec",
    "action": { "type": "command", "command": "npx jest --passWithNoTests" }
  }]
}

{
  "version": "v1",
  "hooks": [{
    "name": "Protect Production Config",
    "trigger": "PreToolUse",
    "matcher": "fs_write|str_replace",
    "action": {
      "type": "command",
      "command": "bash -c 'INPUT=$(cat); if echo \"$INPUT\" | grep -q \"environment.prod\"; then echo \"Modifying production config requires confirmation\" >&2; exit 2; fi; exit 0'"
    }
  }]
}

---
name: commit-message
description: Generate a commit message from the current changes
argument-hint: "Any extra context about this change?"
---

## Generate Commit Message

1. Get the current branch: `git rev-parse --abbrev-ref HEAD`
2. Get the diff: `git diff --cached` (or `git diff` if nothing staged)
3. Format as:

```
[branch-name] Short imperative title (max 72 chars)

- What changed (files/areas)
- Why it changed (intent)
- Any trade-offs or decisions made
```

---
name: new-feature
description: Scaffold a new feature module with component, service, routes, and tests
argument-hint: "Feature name, e.g. 'user-settings'"
---

## Scaffold New Feature

When asked to create a new feature:

1. Create directory: src/app/features/{name}/
2. Generate:
   - {name}.component.ts (standalone, OnPush)
   - {name}.service.ts (inject HttpClient)
   - {name}.routes.ts (lazy-loaded route)
   - {name}.component.spec.ts (Testing Library)
3. Register the route in app.routes.ts
4. Run lint and tests

{
  "mcpServers": {
    "project-docs": {
      "command": "node",
      "args": ["./tools/docs-mcp-server/dist/index.js"],
      "disabled": false
    }
  }
}

---
description: Explore and analyse code without making changes
tools:
  - read_file
  - grep_search
  - file_search
  - list_directory
---

You are a read-only research agent for this Angular project.
Explore the codebase and provide analysis. You cannot modify files or run commands.
When investigating, always check: component hierarchy, service dependencies, route structure.