Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
A skill your agent uses to validate DAE artifacts for schema correctness and cross-artifact consistency.
MITAuto-check passed
Install Consistency Check
$ npx skills add swingerman/engineer --skill consistency-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swingerman/engineer consistency-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineer/skills/consistency-check .claude/skills/consistency-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .claude/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add swingerman/engineer --skill consistency-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swingerman/engineer consistency-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineer/skills/consistency-check .agents/skills/consistency-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .agents/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swingerman/engineer --skill consistency-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swingerman/engineer consistency-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineer/skills/consistency-check .cursor/skills/consistency-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .cursor/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/swingerman/engineer.git --path engineer/skills/consistency-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add swingerman/engineer --skill consistency-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swingerman/engineer consistency-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineer/skills/consistency-check .gemini/skills/consistency-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .gemini/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install swingerman/engineer consistency-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add swingerman/engineer --skill consistency-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineer/skills/consistency-check .github/skills/consistency-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .github/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swingerman/engineer --skill consistency-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swingerman/engineer consistency-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swingerman/engineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineer/skills/consistency-check .opencode/skills/consistency-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "consistency-check" agent skill from https://github.com/swingerman/engineer/tree/master/engineer/skills/consistency-check into .opencode/skills/consistency-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consistency-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
consistency-check- GitHub stars
- 154
- Token cost
- ~1.3k tokens
- SKILL.md length
- 534 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to validate DAE artifacts for schema correctness and cross-artifact consistency.
- Works in 3 steps: Run the judgment checks (below) — the… → Report — errors first, then warnings;… → Handoff — emit a summary.
- Validate DAE artifacts for schema correctness and cross-artifact consistency
- SKILL.md covers When to use, Workflow, Handoff and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Consistency Check is an agent skill from swingerman/engineer. Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers — "/engineer.consistency-check", "check consistency", "validate the artifacts", "are the specs and ACs in sync", "audit this feature".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Disciplined Agentic Engineering — a methodology kit for Claude Code: acceptance-test-first specs, explicit checkpoints, and autonomy you can actually leave running. The engineer… The licence is MIT.
When your agent uses it
- Validate DAE artifacts for schema correctness and cross-artifact consistency
- — /engineer.consistency-check
- Check consistency
- Validate the artifacts
Example prompts
- “/engineer.consistency-check”
- “check consistency”
- “validate the artifacts”
- “/consistency-check”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run the judgment checks (below) — the rows the script cannot decide.
- Report — errors first, then warnings; each with location + a suggested fix (which skill to run). Do not apply fixes.
- Handoff — emit a summary.
What it can do on your machine
Read from SKILL.md and the folder at commit 32947eb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
notion.so
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Consistency Check loads about 1.3k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 534 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from swingerman/engineer at commit 32947eb, republished under its MIT licence (© swingerman). 534 words, ~1,315 tokens.
Download SKILL.mdSave it as
.claude/skills/consistency-check/SKILL.md (or your agent's skills folder).- name
- consistency-check
- description
- Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers — "/engineer.consistency-check", "check consistency", "validate the artifacts", "are the specs and ACs in sync", "audit this feature".
consistency-check
Cross-artifact validation for DAE — the methodology's take on Speckit's /analyze. Read-only: reports inconsistencies and suggests fixes; never mutates. Any agent may run it (mechanical validation, not judgment-heavy verification). checkpoint: null.
When to use
Before major pipeline transitions and as a CI gate.
- Feature scope —
/engineer.consistency-check <slug>— one feature's artifacts - Project scope —
/engineer.consistency-check --project— project-wide invariants
Not for: fixing inconsistencies (run the suggested fix skill); within-one-artifact ambiguity (clarify); code risk (crap-analyzer).
Workflow
- Resolve + load — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md). Feature scope: load every artifact infeatures/NNN-<slug>/+CHARTER.md. Project scope: loadCHARTER.md+ everyfeature.mdfrontmatter. For identifier lookups (does symbol X actually exist in the code?), prefer LSP find-definitions / workspace-symbols when an LSP MCP capability is available; fall back to grep + Read otherwise. See${CLAUDE_PLUGIN_ROOT}/references/code-lookup.md. 1.5. Run the mechanical checks first —${CLAUDE_PLUGIN_ROOT}/scripts/dae_ontology.py <feature-dir>(or--project). It executes every constraint that is a set operation over structured data — enumerations, functional properties, parent/child inverses, cycle detection, AC↔scenario coverage closure, Principle 7 disjointness — deterministically. Take its findings as given; do not re-derive them by reading the artifacts. They are tagged in the tables below as (ontology). See${CLAUDE_PLUGIN_ROOT}/references/ontology.md. - Run the judgment checks (below) — the rows the script cannot decide.
- Report — errors first, then warnings; each with location + a suggested fix (which skill to run). Do not apply fixes.
- Handoff — emit a summary.
Feature-scope checks
| Check | Severity |
|---|---|
feature.md slug matches folder name (ontology) | error |
feature.md mandatory frontmatter present; status: ready ⇒ autonomy_level set (ontology) | error |
acs.md AC IDs unique + sequential; ac_count matches actual (ontology) | error |
Every AC has a covering @AC-N spec scenario; no scenario tags an AC that doesn't exist (ontology) | error |
acs.md ACs in domain language (implementation-leakage heuristic) | warning |
acs.md ACs cover the feature.md outcome | warning |
relevant_adrs reference ADRs that exist | error |
spec.md and .build/spec.json agree | error |
plan.md Charter Check: every ⚠️ deviation has a matching amendment | error |
Validation method honored? — if feature.md declares a non-default validation_method, plan.md's Test strategy section must reference it (canary phase, dashboard names, rollback trigger, etc. as relevant) | warning |
Verification handoffs: agent_id ≠ implementer's (Principle 7) (ontology) | error |
tracker_ref resolves on the configured tracker | warning |
Handoff completeness: no checkpoint marked done in progress.md lacks a complete handoff | error |
parent_feature set ⇒ parent resolves and lists this in child_features (ontology) | error / warning |
Show full SKILL.md (157 more words)Show less
The handoff-completeness check is the after-the-fact sweep for handoff-as-gate
(Foundation Design Section 5): run ${CLAUDE_PLUGIN_ROOT}/scripts/dae_handoff.py <feature-dir> — it flags any checkpoint marked done with a missing,
interrupted, or unmet-exit_criteria handoff.
Project-scope checks
| Check | Severity |
|---|---|
CHARTER.md section 5 roles == manifest.team.default_roles | error |
manifest.yml schema valid; enum values legal | error |
| Feature folder numbering monotonic; no reuse (ontology) | warning |
| One feature branch per feature; one feature per roadmap item (ontology) | warning |
parent_feature chains do not cycle (ontology) | error |
| ADR not referenced by any feature in N months (N from manifest, default 6) | warning |
Every features/*/ has a non-empty feature.md | warning |
team.default_roles includes verifier when independence enforced | error |
Handoff
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts: []. Feature scope → handoff in that feature's handoffs/; --project scope → handoff in .engineer/handoffs/. Any errors → human_action_needed: yes. recommended_next: resolve via clarify / feature-edit / plan, then re-run.
References
${CLAUDE_PLUGIN_ROOT}/references/ontology.md— the (ontology) rows: whatdae_ontology.pydecides and why the rest stays here- Foundation Design — every schema checked here
- Tracker Integration —
tracker_refresolution
© swingerman, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in engineer/skills/consistency-check of swingerman/engineer.
Open the folder on GitHubat commit 32947eb
Compare with similar skills
Consistency Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Consistency Check this skillswingerman/engineer | 154 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Buildernexu-io/open-design | 100k | — | ~337 | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Buildersickn33/agentic-awesome-skills | 47k | 3 repos | ~824 | Automated safety check: Pass | Apache-2.0 | |
| Correctcursor/plugins | 10k | 3 repos | ~612 | Automated safety check: Pass | None |
Similar skills
- Official
Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Web Artifacts Builder
nexu-io/open-design
Build complex claude.ai HTML artifacts with React and Tailwind.
Web Artifacts Builder
sickn33/agentic-awesome-skills
To build powerful frontend claude.ai artifacts, follow these steps:
- Official
Correct
cursor/plugins
Find the mistakes agents keep repeating in this repo and make each one impossible.
Correction
NxcoreAI/EverRoom
Compute Room overview corrections—citation corrections as per-claim edits and general corrections as a single proposal.
More from swingerman/engineer
All 27 skills in this repoCrap Analyzer
swingerman/engineer
A skill your agent uses to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods.
Atdd Mutate
swingerman/engineer
A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.
Fix
swingerman/engineer
A skill your agent uses to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end.
Atdd
swingerman/engineer
A skill your agent uses to drive feature work through the Acceptance Test Driven Development workflow — Given/When/Then specs before code, a project-specific test pipeline, and two parallel test…
Harden
swingerman/engineer
Use after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it, to formally check its invariants — Checkpoint 8.
Next
swingerman/engineer
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project.
Questions about Consistency Check
What does Consistency Check do?
A skill your agent uses to validate DAE artifacts for schema correctness and cross-artifact consistency. Consistency Check is an agent skill from swingerman/engineer. Use to validate DAE artifacts for schema correctness and cross-artifact consistency.
When should I use Consistency Check?
Consistency Check fits situations like: validate DAE artifacts for schema correctness and cross-artifact consistency; — /engineer.consistency-check; check consistency; validate the artifacts.
How do I install Consistency Check in Claude Code?
Run `npx skills add swingerman/engineer --skill consistency-check -a claude-code`. Or copy the skill folder (engineer/skills/consistency-check in swingerman/engineer) into .claude/skills/consistency-check in your project. Claude Code loads it when a task matches its description.
How do I install Consistency Check in Codex?
Run `npx skills add swingerman/engineer --skill consistency-check -a codex`. Or copy the skill folder (engineer/skills/consistency-check in swingerman/engineer) into .agents/skills/consistency-check in your project. Codex loads it when a task matches its description.
Can I use Consistency Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add swingerman/engineer --skill consistency-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/consistency-check, .gemini/skills/consistency-check, .github/skills/consistency-check and .opencode/skills/consistency-check in your project.
What does Consistency Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Consistency Check is instructions for the agent only.
Does Consistency Check access the network?
SKILL.md names 1 domain. As links in the text: notion.so. This is read from the text; nothing was executed.
Is Consistency Check safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Consistency Check use?
Consistency Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Consistency Check use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Consistency Check?
Skills that share tags, products or a category with Consistency Check: Artifacts Builder (nexu-io/open-design, 100k stars), Web Artifacts Builder (anthropics/skills, 180k stars), Web Artifacts Builder (nexu-io/open-design, 100k stars) and Web Artifacts Builder (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Consistency Check?
swingerman (a GitHub user) maintains it in swingerman/engineer, which has 154 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 23, 2026.
Source: swingerman/engineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.