How do I install the Narraitor Pattern Alignment Skill skill?

Run npx skillmds@latest add jerseycheese/narraitor-pattern-alignment-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Narraitor Pattern Alignment Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Narraitor Pattern Alignment Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Narraitor Pattern Alignment Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Narraitor Pattern Alignment Skill?

jerseycheese (@jerseycheese) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Narraitor Pattern Alignment Skill by jerseycheese

Name: Narraitor Pattern Alignment Skill
Rating: 4.2 (5 reviews)
Author: jerseycheese

Narraitor Pattern Alignment Skill

Automatically run after any code change in this repo (components, stores, API routes, CSS, tests, types). Triggers on: new files, refactors, feature additions, or any edit touching src/. Reviews changes for alignment with established project patterns — design tokens, state conventions, error handling, domain boundaries, accessibility. Do NOT wait for user to ask; run as a post-edit check before committing.

jerseycheese 6d92411 4 files · 7.2 KB Updated Sep 10, 2026

File contents

When to invoke (auto-trigger)

Invoke automatically whenever:

A .tsx, .ts, .css, or .test.* file under src/ is created or substantially edited
A new component, store, or API route is added
A refactor touches more than one file

Do NOT invoke for: documentation-only edits, config changes, or trivial one-line fixes.

Narraitor Pattern Alignment

Review workflow

Confirm the scope (files, feature, or diff) before reviewing.
Check for existing utilities or patterns before suggesting new code.
Evaluate the change against the core alignment areas below.
Report issues first (ordered by severity) with file:line and concrete fixes.

Core alignment areas

Components and structure (naming, file size, DOM clarity)
Design tokens and color usage (no hardcoded colors; use var(--color-*) directly, but wrap status/domain tokens like --success/--alignment-* in hsl(var(--...)) — see public_docs/design-system/design-tokens.md)
Error handling and user-friendly errors
State management and persistence patterns
Type safety and domain types
Testing (behavior-first, Testing Library queries)
Accessibility (WCAG 2.1 AA)
Domain boundaries and cross-domain coordination
Docs style (if docs touched)

Output format

Issues first, ordered by severity, with file:line references.
Call out missing tests explicitly.
Briefly list aligned patterns after issues.

References

references/patterns.md (detailed checks and examples)
references/accessibility.md
references/utilities.md

---name: narraitor-pattern-alignment-skilldescription: Automatically run after any code change in this repo (components, stores, API routes, CSS, tests, types). Triggers on: new files, refactors, feature additions, or any edit touching src/. Reviews changes for alignment with established project patterns — design tokens, state conventions, error handling, domain boundaries, accessibility. Do NOT wait for user to ask; run as a post-edit check before committing.---## When to invoke (auto-trigger)Invoke automatically whenever:- A `.tsx`, `.ts`, `.css`, or `.test.*` file under `src/` is created or substantially edited- A new component, store, or API route is added- A refactor touches more than one fileDo NOT invoke for: documentation-only edits, config changes, or trivial one-line fixes.# Narraitor Pattern Alignment## Review workflow- Confirm the scope (files, feature, or diff) before reviewing.- Check for existing utilities or patterns before suggesting new code.- Evaluate the change against the core alignment areas below.- Report issues first (ordered by severity) with file:line and concrete fixes.## Core alignment areas- Components and structure (naming, file size, DOM clarity)- Design tokens and color usage (no hardcoded colors; use `var(--color-*)` directly, but wrap status/domain tokens like `--success`/`--alignment-*` in `hsl(var(--...))` — see `public_docs/design-system/design-tokens.md`)- Error handling and user-friendly errors- State management and persistence patterns- Type safety and domain types- Testing (behavior-first, Testing Library queries)- Accessibility (WCAG 2.1 AA)- Domain boundaries and cross-domain coordination- Docs style (if docs touched)## Output format- Issues first, ordered by severity, with file:line references.- Call out missing tests explicitly.- Briefly list aligned patterns after issues.## References- `references/patterns.md` (detailed checks and examples)- `references/accessibility.md`- `references/utilities.md`

Frequently asked questions