chitolabs/ai-skill-pack/angular-developer

Activation Contract

Use this skill when the user request matches angular-developer or the preserved source description: Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Before acting, read references/source-skill.md and any relevant companion files listed in References. Treat those files as the source-specific workflow and this file as the portable runtime contract.

Hard Rules

• Defer to the user, to repository policy, and to any managed workflow that owns the current phase, gate, artifact, review, or verdict. Never claim workflow authority or create a parallel plan, review, or verdict.
• Every path is relative to this skill: never absolute, never a runtime install directory, never another skill. Name a companion skill, never depend on one; if it is not installed, say so and continue with this skill's own references or the closest manual fallback.
• Preserve the source skill's domain behavior, prerequisites, warnings, and output expectations.
• Do not install, deploy, authenticate, mutate remote services, or run destructive commands unless the preserved workflow requires it and the user has approved the action.
• Use capability wording: available file editing tool, available shell/terminal tool, available browser tool, and if persistent memory is available.
• Prefer current official documentation or source retrieval when the preserved workflow says knowledge may be outdated.
• Keep all generated artifacts inside the user-requested workspace unless the user explicitly names another destination.

Decision Gates

Execution Steps

1. Match the user request to the preserved source workflow in references/source-skill.md.
2. Inspect any local companion reference needed for the specific task.
3. Verify prerequisites, credentials, project context, and safety boundaries before tool use.
4. Execute the smallest correct workflow using the host runtime's available tools.
5. Validate the result with the checks named in the preserved source guidance or with an explicit manual verification note.

Output Contract

Return the completed action, files or commands used, verification evidence, blockers, and any next step the user must approve. If the task is blocked, state the exact missing prerequisite or unsafe condition.

References

• references/source-skill.md - preserved upstream skill body and domain workflow.
• references/ - 36 preserved source companion files.
• references/companion-index.md - the complete list of those files.