A collection of agent skills for Claude Code. Each skill is a folder containing a SKILL.md with frontmatter (name, description) and instructions that Claude loads on demand when the task matches.
Service layer architecture guidance. Enforces a two-layer separation where actions orchestrate domain rules (the "why/when") and a service layer centralizes reusable operational mechanics (the "how").
Use it when:
- Multiple workflows duplicate the same operational logic
- You're deciding what belongs in actions vs. shared services
- A bug fix in one flow doesn't propagate to others doing the same thing
- Adding a feature that shares mechanics with existing ones
Includes a migration checklist for extracting shared logic safely and a table of anti-patterns to avoid (god services, leaky services, over-abstraction).
Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue.
Use it whenever a UI change needs verifiable evidence that it works, instead of prose claims.
Requires a GUI environment with screen recording, an authenticated browser session for the app under test, and the
ghCLI (or equivalent) for posting evidence.
Clone the repo and copy (or symlink) a skill folder into your skills directory:
# Available in all projects
cp -r code-structure ~/.claude/skills/
# Or scoped to a single project
cp -r code-structure /path/to/project/.claude/skills/Claude Code picks up the skill automatically and invokes it when a task matches the skill's description. You can also invoke one explicitly with /code-structure or /evidence-driven-testing.
- Create a folder named after the skill (kebab-case).
- Add a
SKILL.mdwithnameanddescriptionfrontmatter — the description is what Claude uses to decide when the skill applies, so make it trigger-focused ("Use when..."). - Keep instructions concise and actionable; link out to reference files in the folder if they get long.