Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides language-agnostic coding principles and quality gates designed for backend and infrastructure engineers. It structures the process of detecting code smells, debugging failures, and ensuring implementation completeness.
The workflows help developers determine the necessary documentation scope for changes—including ADRs and design docs—while applying rigorous criteria to maintainability and readability during feature implementation and refactoring.
WHO IT'S FOR
Backend / infrastructure engineers
applying technical decision criteria and anti-pattern detection
Technical leads / architects
defining documentation scope and technical design requirements
AI agent / automation builders
integrating coding principles into AI workflows
Platform / DevEx teams
managing external resource context and API schemas
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Backend/general workflow plugin
Installs: Installs the complete `dev-workflows` plugin for backend, API, CLI, and general-purpose workflows. Install only one workflow plugin. · Claude Code
Before you start
A Claude Code release with plugin marketplace support
In a terminal, start Claude Code.
claude
In the Claude Code session, add the author's plugin marketplace.
Installs: Installs the complete `dev-workflows-frontend` plugin for React and TypeScript frontend workflows. Install only one workflow plugin. · Claude Code
Before you start
A Claude Code release with plugin marketplace support
In a terminal, start Claude Code.
claude
In the Claude Code session, add the author's plugin marketplace.
Installs: Installs the complete `dev-workflows-fullstack` plugin, which already contains the backend and frontend workflows. Install only one workflow plugin. · Claude Code
Before you start
A Claude Code release with plugin marketplace support
In a terminal, start Claude Code.
claude
In the Claude Code session, add the author's plugin marketplace.
Installs: Adds the marketplace and installs the complete `dev-workflows-fullstack` plugin at project scope so the resulting `.claude/settings.json` can be committed for contributors. The full-stack plugin contains the backend and frontend workflows. · Claude Code
Before you start
A Claude Code release with plugin marketplace support
Run from: The target project repository
From a terminal in the target project repository, add the marketplace at project scope.
claude plugin marketplace add shinpr/claude-code-workflows --scope project
From a terminal in the same repository, install the full-stack workflow plugin at project scope.
claude plugin install dev-workflows-fullstack@claude-code-workflows --scope project
Commit the resulting `.claude/settings.json` if you want contributors to be prompted to use the same workflow plugin.
The repository to inspect as the current working repository
Any requested policy boundary or quality concern to prioritize
Use the `recipe-quality-profile` skill to inspect this repository and propose a small initial set of repository-specific implementation and review acceptance conditions. Show supporting and contradicting evidence, omitted candidates, and unresolved policy choices. Do not write `docs/project-context/quality.yaml` until I explicitly confirm the complete proposal.
One external resource to document, such as a design source, design system, API schema, secret store, or IaC source
Known URL, MCP name, file path, or access command, if available
Use the `external-resource-context` skill to conduct the required interactive hearing for one external resource this project depends on, then propose its project-tier record for `docs/project-context/external-resources.md`. Start with the resource's label, type, canonical location, and access method; do not invent unavailable access details.
Relevant requirements or public interfaces that must remain unchanged
Check the repository for this skill’s setup.
Use the `coding-principles` skill to review the specified file or small module. Report up to five concrete maintainability or readability issues, cite the relevant code locations, and suggest the smallest improvement for each. Do not edit the code.