testing Skills

Generic stakeholder discovery template for creating new project-specific stakeholder skills. Auto-invoke when user reque...

Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignm...

Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You nee...

Identify stale cache issues across browser cache, CDN layers, API response caching, and application-level caches that ca...

Compare recurring implementation patterns, choose the best existing approach, teach it in the owning skill, and enforce...

Provide repo coding standards.

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, fo...

Comprehensive testing patterns for modern TypeScript applications covering Vitest, React Testing Library, Playwright E2E...

Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real be...

Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked ex...

This skill should be used when the user wants the business suite dashboard, guidance on where to start or what to do nex...

Use this skill when the user runs /start, says "start", "enable the SDLC workflow", "I want to build", "I want to fix",...

Use when responding to any user request — entry point into grimoire. Routes the input to the matching grimoire workflow...

Start a review session from an existing plan and implementation. Discovers available plans, validates implementation exi...

Implement one Pieceful task spec end to end (read context, build, test, review, Definition of Done) and stop for the own...

Profile and optimize application startup time for desktop applications

| ID | static-analysis |

Static code analysis tools and patterns

Use when changing the static web app, Pyodide loading, staged Python files, browser contracts, or GitHub Pages deploymen...

Analyze source code statically to detect potential functional bugs including null dereferences, incorrect condition chec...

Creates, reviews, and modernizes static code analysis setups for Node.js and TypeScript repositories, covering ESLint fl...

Verify code correctness statically against specifications using type checking, contract verification, and formal methods...

Probability, distributions, hypothesis testing, and statistical inference. Use for A/B testing, experimental design, or...

Comprehensive statistics expert covering probability theory, distributions, hypothesis testing, regression, and Bayesian...

Show a read-only rollup of the definition of done — every exit condition with its state, properties, and open reason — w...

Change conviction level or status on a single thesis. Use when user says "change conviction", "downgrade", "upgrade", "m...

Display Studio Engine status dashboard. Shows version, edition, creator profile, products with scores, and stale warning...

Before making changes, verifies they match what was actually requested. Activates when about to modify files, add featur...

Zuko's steady flame for vetting a performance number. A flame that flickers is not a measurement. Use for benchmark-chec...

Adapt LLMs efficiently by composing multiple pre-existing semantic steering vectors via Bayesian optimization, balancing...

Use when hitting the same error after 2+ fix attempts, when multiple symptoms share a common system, or when fixes feel...

Applies stewardship virtues (Care, Curiosity, Humility, Diligence) to plugin work. Use when authoring plugins or reviewi...

Use when building a screen to find candidates. Covers screen design, criteria that actually discriminate, avoiding overf...

Teaches storage for DevOps: block/file/object, CSI, PV/PVC, durability, performance tiers, and backup patterns. Use when...

Run a storefront performance audit with Lighthouse and Core Web Vitals analysis

Analyze, diagnose, and reorganize story tree structure. Use when user says "check tree health", "find orphans", "move st...

Before marking any story as complete, follow this validation ceremony to ensure the work is truly done and meets quality...

Use when an implemented story needs evidence-backed acceptance, deviation, test, review, and completion gating.

Design or replace lean CI around tester.army e2e, isolated Neon branches, and native TesterArmy Linear issue export. Use...

Review user stories for quality, proper sizing, sequencing, and acceptance criteria. Use before converting to prd.json....

Use when a story must be checked for implementation readiness, traceability, dependencies, acceptance clarity, or open d...

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes,...

[Code Quality] Review user stories for completeness, coverage, dependencies, and quality before implementation. AI self-...

Create a storyboard with structured process, quality checks, and system integration

Render a shotkit storyboard (shots.json, text-overlays.json, brand-lock.snapshot.md) into one self-contained HTML previe...

Use when reviewing storyboard outputs at any production stage (beat breakdown, beat board, sequence board, motion prompt...

Testing UI components through Storybook stories with play functions, interaction testing, accessibility checks, and visu...

Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix...