feat(lfx): scaffold angular 20 ssr app with express server

.claude/rules/skill-guidance.md

@@ -5,44 +5,62 @@ globs: '*'
 
 # Available Skills
 
-This project has guided skills for common workflows. **Proactively suggest the relevant skill** when a user's request matches one of these:
+This project has guided skills for `apps/lfx` (the primary app). **Always route through `/lfx` as the entry point** — it classifies intent and delegates to the right specialist skill.
 
-| Skill        | When to Suggest                                                                                                               |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------- |
-| `/setup`     | Getting started, first-time setup, broken environments, install failures, missing env vars, 1Password, how to run the app     |
-| `/develop`   | Add a feature, fix a bug, modify code, create components/services/endpoints/types, refactor, build, implement any code change |
-| `/preflight` | Before submitting a PR, check if code is ready, validate changes, verify a branch, finished development, review readiness     |
+---
+
+## Entry Point
 
-## Trigger Phrases
+| Skill  | When to Suggest                                                                            |
+| ------ | ------------------------------------------------------------------------------------------ |
+| `/lfx` | **Always** — any request related to `apps/lfx` development, research, setup, or validation |
 
-**`/setup`** — match any of these intents:
+**`/lfx` is the default entry point for ALL work.** It auto-detects what the user needs and routes to the right specialist skill. Users never need to know about the specialist skills below.
 
-- "How do I set up?", "Getting started", "First time here"
-- "yarn install fails", "corepack error", "node version"
-- "env vars", "1Password", "app won't start"
-- "broken environment", "fresh install", "missing dependencies"
+### Trigger Phrases
 
-**`/develop`** — match any of these intents:
+- Any code change: "Add a feature", "Fix this bug", "Build a component", "Implement this Figma URL"
+- Research: "What endpoints exist?", "How does X work?", "Does the API support Y?"
+- Validation: "Ready for PR", "Check my code", "Preflight"
+- Setup: "Set up my environment", "Install", "Getting started"
 
-- "Add a feature", "Create a component", "Build an endpoint"
-- "Fix this bug", "Modify the service", "Update the page"
-- "Refactor", "Implement", "Change the behavior"
-- "New interface", "Add a filter", "Create a form"
-- Describes any code change, feature request, or bug fix
+---
 
-**`/preflight`** — match any of these intents:
+## Specialist Skills (routed by `/lfx` — rarely invoked directly)
 
-- "Ready for PR", "Check my code", "Validate changes"
-- "Before I submit", "Is my branch ready?", "Review my work"
-- "Run checks", "Lint and build", "Pre-PR validation"
-- Any indication that development work is finished
+| Skill                  | Purpose                                                                        |
+| ---------------------- | ------------------------------------------------------------------------------ |
+| `/lfx-coordinator`     | Plans and delegates code changes — routes to builder skills                    |
+| `/lfx-design`          | Builds base UI components (buttons, inputs, cards) from Figma                  |
+| `/lfx-research`        | Read-only exploration — upstream API validation, codebase discovery            |
+| `/lfx-backend-builder` | Generates Express proxy endpoints, services, controllers, routes, shared types |
+| `/lfx-ui-builder`      | Generates Angular frontend components, services, pages                         |
+| `/lfx-preflight`       | Pre-PR validation — lint, build, license headers                               |
+| `/lfx-setup`           | Environment setup — prerequisites, install, env vars, dev server               |
 
-## For Cowork Sessions
+## Skill Hierarchy
 
-Non-developer contributors use these skills as guided workflows. Follow these rules:
+```text
+/lfx (entry point — classifies intent, routes)
+  ├── /lfx-coordinator (plans + delegates code changes)
+  │     ├── /lfx-research    (read-only exploration)
+  │     ├── /lfx-design      (base UI components)
+  │     ├── /lfx-ui-builder  (feature components)
+  │     └── /lfx-backend-builder (Express proxy code)
+  ├── /lfx-research   (direct research without building)
+  ├── /lfx-preflight   (pre-PR validation)
+  └── /lfx-setup       (environment setup)
+```
+
+**Key rules:**
+
+- `/lfx` routes via Agent subagents — never inline Skill calls
+- `/lfx-coordinator` delegates via Agent subagents — never writes code itself
+- Builder skills (`/lfx-design`, `/lfx-ui-builder`, `/lfx-backend-builder`) are the only skills that write code
+- No skill should call Figma MCP tools inline — only `/lfx-design` calls them within its Agent subprocess
+
+## For Cowork Sessions
 
-- If the user describes a feature they want to build, suggest `/develop` — it walks them through the full process step-by-step
-- If the user asks about setup or getting started, suggest `/setup`
-- After any development work is complete, remind them to run `/preflight` before creating a PR
-- If you are unsure which skill applies, ask the user what they're trying to accomplish
-- When a skill references architecture docs in `docs/`, read those docs before generating code — they are the source of truth
+- Contributor describes any task → suggest `/lfx`
+- After development work → remind to run `/lfx-preflight` (or let `/lfx` suggest it)
+- When a skill references architecture docs in `docs/`, read those docs before generating code

.claude/settings.json

@@ -11,5 +11,8 @@
         ]
       }
     ]
+  },
+  "enabledPlugins": {
+    "figma@claude-plugins-official": true
   }
 }