project-standalo-note-to-app/.claude/commands/guardrail/design.md

description	allowed-tools
Design a new feature by adding entities to manifest (Architect mode)	Read, Write, Bash

Design Feature (Architect Mode)

🏗️ ARCHITECT MODE ACTIVATED

Design the feature: "$ARGUMENTS"

CRITICAL RULES

You are now acting as the ARCHITECT AGENT.

✅ ALLOWED:

• Read any file
• Write to project_manifest.json ONLY
• Run validation scripts

❌ BLOCKED:

• Write ANY code files (.ts, .tsx, .css, .sql, .js, .jsx)
• You CANNOT write implementation code yet

Workflow

1. Verify Phase: Check project_manifest.json - must be in DESIGN_PHASE

2. Analyze Requirements: Break down "$ARGUMENTS" into:

   • Pages needed (routes/screens)
   • Components needed (UI elements)
   • API endpoints needed (backend routes)
   • Database tables needed (data storage)

3. Define Each Entity in manifest with:

   • Unique ID following naming convention
   • Complete specification (props, schemas, columns)
   • status: "DEFINED"
   • File path where it will be implemented

4. Update Manifest: Add all entities to project_manifest.json

5. Validate: Run python3 skills/guardrail-orchestrator/scripts/validate_manifest.py

6. Summarize: List what was added and suggest /guardrail:review

Entity Templates

Page

{
  "id": "page_[name]",
  "path": "/[route]",
  "file_path": "src/pages/[name]/index.tsx",
  "status": "DEFINED",
  "components": [],
  "data_dependencies": []
}

Component

{
  "id": "comp_[name]",
  "name": "[PascalCase]",
  "file_path": "src/components/[Name]/index.tsx",
  "status": "DEFINED",
  "props": {}
}

API Endpoint

{
  "id": "api_[action]_[resource]",
  "path": "/api/v1/[resource]",
  "method": "GET|POST|PUT|DELETE",
  "file_path": "src/api/[resource]/[action].ts",
  "status": "DEFINED"
}