Skip to content
v0.2.0MIT

CodingOnRails workflow: setup, think, research, plan, code, test, work router, plus design, review, refactor and docs phases

cor-code

Code phase of the COR methodology. Implements tasks from the plan sequentially and autonomously, running all configured checks after each task and committing per task when Auto Commit is enabled. Pauses only when tool/command output reveals unexpected high-impact information. Maintains concise repo instructions by updating active rules and archiving historical notes after each task. Claude Code users: invoke as /cor:cor-code [task-id].

cor-design

Exploratory UI design phase of the COR methodology. Captures visual goals and constraints, generates three comparable lightweight web variants, scores them, and produces a decision-ready direction before implementation planning. Use when the user wants to explore visual directions, compare UI options, redesign a screen or app shell, or needs a design direction settled before cor-plan. Claude Code users: invoke as /cor:cor-design.

cor-docs

Updates a project's Markdown documentation from a git diff between two branches plus the existing codebase, following the Diataxis framework (tutorials, how-to guides, reference, explanation). Edits only the quadrants the change actually affects, asks the user when intent is missing, and keeps output compatible with MkDocs and Zensical. Initializes the docs directory (default docs/) when absent. Use when the user asks to document a branch, update docs from a diff or PR, sync documentation with code changes, set up Diataxis docs, or mentions Diataxis, MkDocs, or Zensical. Claude Code users: invoke as /cor:cor-docs.

cor-plan

Plan phase of the COR methodology. Takes the understanding built in the Think phase and turns it into a structured, ordered task list saved to .cor/plan.md (or agent memory / session tasks). No coding happens here — only decomposition and sequencing. Claude Code users: invoke as /cor:cor-plan.

cor-refacto

Think+Plan skill for behavior-preserving refactoring. Use when the user wants to improve readability, simplicity, maintainability, duplication, or coupling without functional changes. Produces a concrete refactor plan and a strict handoff for cor-code; blocks theoretical refactors that do not reduce net complexity. Claude Code users: invoke as /cor:cor-refacto.

cor-research

Researches current libraries, version-specific APIs, architecture practices, and implementation options after COR Think and before COR Plan. Use when implementation depends on maintained third-party packages, recent platform capabilities, external standards, security guidance, or an evidence-based architecture choice.

cor-review

Measured code review that ends in a behavior-preserving refactor plan. Combines cor-refacto's simplification gates with deterministic metrics from Uncle Bob's crapper, dryer and mutator CLIs (CRAP per function, structural duplication, mutation testing). Use when the user asks to review or audit a codebase for refactoring, asks what is worth refactoring, mentions complexity, coverage, duplication, mutation score, CRAP, dryer, crapper, or mutator, or wants a refactor plan backed by numbers. Writes no code; hands off to cor-code. Claude Code users: invoke as /cor:cor-review.

cor-setup

Initialize a project for the COR (CodingOnRails) methodology. Detects the tech stack, proposes check commands, and writes a .cor/config.md file. Run once per repo before using any other COR skills. Claude Code users: invoke as /cor:cor-setup.

cor-test

Test phase of the COR methodology. Runs only the tests that were explicitly planned — unit, integration, and UAT. No unplanned testing scope creep. Claude Code users: invoke as /cor:cor-test.

cor-think

Deep interrogation phase of the COR methodology. Ask the user focused questions across problem definition, scope, constraints, risks, and acceptance criteria before any planning or coding begins. Produces a confidence summary after each round. Claude Code users: invoke as /cor:cor-think.

cor-work

Entry point for the COR (CodingOnRails) methodology. Detects current project state, shows a compact progress summary, and routes to Think, optional Research, Plan, Code, or Test. Use when starting or resuming work, recovering an interrupted task, or checking what comes next. Claude Code users: invoke as /cor:cor-work.

ui-design-system-principles

Applies design-token, color, typography, spacing, and accessibility systems to frontend output. Use for any UI creation or restyling task — components, pages, dashboards, forms, charts, data tables — even when the user never says 'design system', and when they ask to make it look better, improve the design, or fix the styling.

ux-frameworks

Applies and cites the five canonical UX evaluation frameworks — Nielsen's heuristics, Garrett's Five Planes, Gestalt/PARC, Morville's Honeycomb, Yablonski's Laws of UX. Use for UX critiques, heuristic evaluations, design reviews, interface audits, diagnosing why a design "feels off", choosing the right framework for a UX problem, or producing UX deliverables; also when any of those framework names is mentioned.