howells
67 verified skills1,066 total stars
testing
Characterization testing and safety-net backfill for existing code. Use when legacy, under-tested, or risky code needs tests before a refactor, bug fix, or behavior change. Captures current behavior through public interfaces, identifies coverage gaps, and adds focused unit, integration, or E2E tests without replacing TDD implementation workflows.
development22
launch
Go-live and shareability checklist covering the basics needed to make a project visitable, shareable, and ready for a first real audience. Use when asked to "launch", "go live", "make this shareable", "get this ready to show people", or prepare a project for a public URL.
development22
commit
Smart commit, push, and npm publish with auto-splitting across domains. Creates atomic commits. Use when asked to "commit", "push changes", "publish", "save my work", or after completing implementation work. Automatically groups changes into logical commits.
data-ai22
detail
Internal bridge from /arc:ideate feature specs to /arc:implement execution plans. Creates implementation plans with exact file paths, test code, and TDD cycles. Invoked by /arc:implement, not directly.
development22
using-arc
Use when starting any conversation - establishes Arc's skill routing, instruction priority, and bootstrap rules
tools22
review
Run expert review on a plan, spec, or implementation approach with parallel reviewer agents. Presents findings as Socratic questions. Use when asked to "review the plan", "check this approach", or before implementation to validate architectural decisions. Optional argument: reviewer name (e.g., `/arc:review daniel-product-engineer`)
testing22
using-arc
Use when starting any conversation - establishes Arc's skill routing, instruction priority, and bootstrap rules
tools22
audit
Comprehensive codebase audit with verification and specialized reviewers. Generates actionable reports. Use when asked to "audit the codebase", "review code quality", "check for issues", "security review", or "performance audit". By default, run the complete audit: mechanical checks first, then specialist reviewers, then a scored report.
development22
launch
Go-live and shareability checklist covering the basics needed to make a project visitable, shareable, and ready for a first real audience. Use when asked to "launch", "go live", "make this shareable", "get this ready to show people", or prepare a project for a public URL.
development22
testing
Characterization testing and safety-net backfill for existing code. Use when legacy, under-tested, or risky code needs tests before a refactor, bug fix, or behavior change. Captures current behavior through public interfaces, identifies coverage gaps, and adds focused unit, integration, or E2E tests without replacing TDD implementation workflows.
development22
vision
Create, review, or revise a concise project vision document that captures what a project is, who it is for, why it exists, success criteria, constraints, non-goals, and decision principles. Use when starting a new project, clarifying product direction, aligning a codebase for future agent work, defining a north star, or turning a vague idea into docs/vision.md.
development22
implement
Scope-aware implementation workflow with TDD and continuous quality checks. Use when asked to "implement this", "build this feature", "execute the plan", or after /arc:ideate has created a feature spec. For small work it creates a lightweight inline plan; for larger work it creates or loads a full implementation plan and executes task-by-task with build agents.
development22
ideate
Turn ideas into validated feature specs through collaborative dialogue with built-in expert review. Use when asked to "design a feature", "plan an approach", "think through implementation", or when starting new work that needs product and technical shaping before coding.
development22
refactor
Discover architectural friction and propose structural refactors with competing interface options. Focuses on deepening shallow modules, extracting grouped concerns into packages/modules, breaking up god files, reducing duplication, and improving testability. Use when asked to "improve the architecture", "find refactoring opportunities", "deepen modules", "consolidate coupling", "break up god components", "extract this into a package", "make this more testable", or "find architectural friction".
development22
review
Run expert review on a plan, spec, or implementation approach with parallel reviewer agents. Presents findings as Socratic questions. Use when asked to "review the plan", "check this approach", or before implementation to validate architectural decisions. Optional argument: reviewer name (e.g., `/arc:review daniel-product-engineer`)
testing22
ideate
Turn ideas into validated feature specs through collaborative dialogue with built-in expert review. Use when asked to "design a feature", "plan an approach", "think through implementation", or when starting new work that needs product and technical shaping before coding.
development22
implement
Scope-aware implementation workflow with TDD and continuous quality checks. Use when asked to "implement this", "build this feature", "execute the plan", or after /arc:ideate has created a feature spec. For small work it creates a lightweight inline plan; for larger work it creates or loads a full implementation plan and executes task-by-task with build agents.
development22
vision
Create, review, or revise a concise project vision document that captures what a project is, who it is for, why it exists, success criteria, constraints, non-goals, and decision principles. Use when starting a new project, clarifying product direction, aligning a codebase for future agent work, defining a north star, or turning a vague idea into docs/vision.md.
development22
refactor
Discover architectural friction and propose structural refactors with competing interface options. Focuses on deepening shallow modules, extracting grouped concerns into packages/modules, breaking up god files, reducing duplication, and improving testability. Use when asked to "improve the architecture", "find refactoring opportunities", "deepen modules", "consolidate coupling", "break up god components", "extract this into a package", "make this more testable", or "find architectural friction".
development22
detail
Internal bridge from /arc:ideate feature specs to /arc:implement execution plans. Creates implementation plans with exact file paths, test code, and TDD cycles. Invoked by /arc:implement, not directly.
development22
commit
Smart commit, push, and npm publish with auto-splitting across domains. Creates atomic commits. Use when asked to "commit", "push changes", "publish", "save my work", or after completing implementation work. Automatically groups changes into logical commits.
data-ai22
audit
Comprehensive codebase audit with verification and specialized reviewers. Generates actionable reports. Use when asked to "audit the codebase", "review code quality", "check for issues", "security review", or "performance audit". By default, run the complete audit: mechanical checks first, then specialist reviewers, then a scored report.
development22
browse
Browse a web app through an expert persona — evaluate the rendered experience, not just the code. Use when asked to "browse the app", "experience the app", "evaluate the app as a user", or when you want expert-level quality assessment of the rendered product. Supports designer, first-time-user, strategist, and demo-presenter personas. Chrome MCP preferred, agent-browser as fallback.
tools20
document
Generate documentation for your codebase — reference docs for a file, feature guides, or a full documentation site. Use when asked to "document this", "generate docs", "write documentation", "create API reference", or when you need thorough documentation for a module, feature, or entire project. Framework-aware: detects Fumadocs, Nextra, Docusaurus, etc. and generates in the right format.
development20
rules
Apply Arc's coding rules to the current project. Copies rules to .ruler/ directory. Use when asked to "set up coding rules", "apply standards", "configure rules", or when starting a project that should follow Arc's conventions.
tools20
prune-agents
Kill orphaned Claude subagent processes that didn't exit cleanly. Use when asked to "prune agents", "clean up agents", "kill orphaned processes", or when subagents accumulate from Task tool usage.
tools20
brand
Create a visual identity system — palette, typography, tone, and generated assets. Produces 5 distinct brand directions for the user to choose from, then converges to a complete brand system with tokens and assets. Strongly opinionated against generic tech aesthetics. Use when asked to "create a brand", "define the visual identity", "design the brand", "set up colors and fonts", or before /arc:design for new projects.
data-ai20
seo
Deep SEO audit for web projects. Analyzes codebase for crawlability, indexability, on-page SEO, structured data, social previews, and technical foundations. Optionally runs Lighthouse and PageSpeed against a live URL. Reports findings with severity, offers direct fixes or /arc:detail plans. Use when asked to "audit SEO", "check SEO", "review SEO", or "is my site SEO-ready".
development20
suggest
Opinionated recommendations for what to work on next based on Linear issues, tasks, and codebase. Use when asked "what should I work on", "what's next", "suggest priorities", or when starting a session and unsure where to begin.
development20
letsgo
Production readiness checklist covering domains, SEO, security, and deployment. Use when asked to "ship it", "deploy to production", "go live", "launch", or when preparing a project for production deployment.
development20
deps
Dependency audit, alternative discovery, and batch upgrades with test verification. Use when asked to "check dependencies", "audit packages", "update dependencies", "find outdated packages", or "check for CVEs". Generates a prioritized report, then optionally walks through batch upgrades with rollback on failure.
testing20
ai
AI SDK guidance for building AI-powered features. Loads correct patterns, warns about deprecated APIs, and guides through chat UIs, agents, structured output, and streaming. Use when building AI features, debugging AI SDK errors, or before implementing any AI work.
development20
responsive
Audit and fix responsive/mobile issues across every page of a project, using browser screenshots at two breakpoints (375px mobile, 1440px desktop). Design-aware: reads existing design docs to preserve aesthetic intent, not just "make it fit." Use when asked to "make it responsive", "fix mobile", "responsive audit", or after building a desktop-first UI that needs mobile adaptation.
development20
design
Create distinctive, non-generic UI designs with aesthetic direction and wireframes, or polish existing UI code after implementation. Use when asked to "design the UI", "create a layout", "wireframe this", or when building UI that should be memorable rather than generic. Also handles "clean this up", "componentize this", and other post-implementation polish work. Avoids AI slop patterns.
development20
progress
Internal skill for progress journal management. Other skills append to docs/arc/progress.md for cross-session context. Not invoked directly by users.
documentation17
hooks
Install Claude Code hooks and git hooks for automatic formatting, linting, and context monitoring. Use when setting up a project, after "install hooks", "set up hooks", "add auto-formatting", "add git hooks", "set up husky", or when starting a new project that uses Biome.
development17
go
The main entry point. Understands your codebase and routes to the right workflow. Use when starting a session, saying "let's work on something", or unsure which Arc command to use. Gathers context and asks what you want to do.
development17
help
Show all Arc commands with context-aware relevance. Reads the codebase to understand what's present (framework, tests, plans, design docs, etc.) and annotates each command with whether it's relevant right now. Use when asked "what can arc do", "help", "list commands", "what commands are available", or "how does arc work".
development17
verify
Run sequential verification checks on the current codebase. Build, typecheck, lint, tests, debug log audit, and git status. Stops on critical failures. Supports modes: quick, full, pre-commit, pre-pr.
development16
build
Build small-to-medium features with lightweight planning and full agent orchestration. Use for "build this component", "add this feature", "create this utility" — work that doesn't need full ideate/implement but still deserves proper planning and quality gates.
tools16
harden
Production resilience pass. Addresses error states, text overflow, i18n prep, edge cases, loading states, and input validation. Use when asked to "harden this", "make it production ready", "handle edge cases", or before shipping UI to real users.
tools16
animate
Review a feature and add purposeful animations. Identifies static areas needing feedback, transitions, or delight, then adds motion/react or CSS transitions. Use when asked to "animate this", "add motion", "make it feel alive", or "add transitions".
development16
distill
Strip UI to its essentials. Remove unnecessary complexity, redundant wrappers, excessive nesting, and over-engineered components. Use when asked to "simplify this", "strip it down", "make it cleaner", or when UI feels bloated.
tools16
naming
Generate and validate project names. Reads codebase context, produces candidates using tech naming strategies, and checks domain + GitHub availability. Use when naming a new project, renaming, or validating an existing name.
development16
tidy
Clean up completed plans in docs/arc/plans/. Archives or deletes finished plans. Use when asked to "clean up plans", "tidy the docs", "archive old plans", or after completing implementation to remove stale planning documents.
documentation16
flow
Discover, store, and walk user flows. Scans your codebase for routes and interactive elements, generates walkable flow artifacts, then executes them in Chrome to verify they work. Four modes: discover (scan code → generate flows), walk (execute flows in browser), check (detect drift via file checksums), gaps (identify missing journeys from app signals). Use when asked to "discover flows", "walk the app", "check for drift", "test user journeys", "generate user flows", "what flows am I missing", or "flow gap analysis".
development16
legal
Generate Privacy Policy, Terms of Service, and Cookie Policy pages. Use when setting up legal pages for a new project, when asked to "create privacy policy", "add terms of service", "generate legal pages", or when /arc:letsgo identifies missing legal documents.
development16
polish
Pre-ship visual refinement pass. Checks spacing, state completeness, contrast, typography, and motion quality. Use when asked to "polish this", "clean up the UI", "final pass", or before shipping any UI feature.
testing16
edit
Run line-level editing across chapters. Catches spelling, grammar, awkward phrasing, and word echoes.
tools6
build
Build an EPUB from your fiction project. Compiles chapters, metadata, and optionally a cover image.
development6
new
Start a new fiction project from scratch. Interactive wizard guides you through discovery, architecture, characters, world, and outline.
documentation6
illustrate
Generate consistent chapter illustrations using motif series. Creates a visual style from the cover, builds character references, then generates one illustration per chapter with consistent styling.
development6
fiction
This skill should be used when the user asks to "write a chapter", "write prose", "continue the story", "develop a character", "review my chapter", "critique my manuscript", "write a synopsis", "summarize my story", "plan my novel", "outline my book", "check for consistency", or mentions fiction writing, novels, short stories, scenes, or narrative craft.
development6
critique
Get a full literary critique of your completed manuscript. NYT/New Yorker style.
tools6
status
Quick view of project status without suggestions.
tools6
notes
Collect and process inline editing notes from chapters. Finds %%NOTE:%%, %%EDIT:%%, %%CHECK:%%, and %%CUT:%% markers.
testing6
plan
Design story architecture. Use when starting a new project or rethinking structure.
content-media6
next
Get suggestion for what to work on next.
tools6
synopsis
Generate a synopsis of your manuscript at various lengths. Great for pitches, query letters, or back cover copy.
databases6
reconcile
Audit a project against current plugin conventions and offer to update structure.
tools6
language
Verify non-English phrases in your manuscript. Checks grammar, period accuracy, dialect, and translations.
testing6
cover
Generate book cover art prompts for image generation models. Reads project content and produces optimized prompts for Kindle-dimension covers.
data-ai6
naming
Generate and validate book title options. Produces candidates using proven naming strategies and checks availability against existing books.
testing6
review
Review chapters for coherence, cheesiness, consistency, pace, tone, and character. Suggests specific rewrites.
testing6
outline
Create chapter and scene breakdown. Use after architecture is established.
tools6
character
Create or develop a character document.
development6
go
Resume work on a fiction project. Loads context and suggests what to do next.
development6