skills/dinachi-assistant/SKILL.md
Unified Dinachi skill for fast component integration and plan-first generative UI guidance. Use when users ask to initialize/add Dinachi components, build concrete UI features quickly, map ambiguous product requirements to Dinachi recipes, or validate generated UI plans before implementation.
npx skillsauth add raymond-ui/dinachiui dinachi-assistantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use one skill with two explicit modes and one automatic router.
Use when user asks for concrete implementation quickly:
add dialog + form)Primary references:
references/components.mdreferences/intent-map.mdreferences/workflows.md (command generation and verification)references/troubleshooting.md (setup/import/theme diagnosis)references/maintainer-checklist.md (monorepo component/docs/template/test updates)Primary scripts:
scripts/suggest-components.mjs --json "<prompt>" (when component names are ambiguous)scripts/audit-skill.mjs (maintainer consistency checks)scripts/validate-skill.mjs (skill folder sanity checks)Maintainer scope:
references/maintainer-checklist.md.packages/components/src/<slug> as source of truth and keep CLI templates/docs in sync.Use when user intent is broad/ambiguous or generative:
Primary references:
references/components.registry.jsonreferences/policies.jsonreferences/intent.schema.jsonreferences/recipe.schema.jsonreferences/question-policy.jsonPrimary scripts:
scripts/resolve-intent.mjs --json "<prompt>"status=clarify, run scripts/clarify-question.mjs --json '<GuidanceDecision JSON>'status=resolved, run scripts/plan-recipe.mjs --json '<GuidanceDecision JSON>'scripts/validate-recipe.mjs --json '<UIRecipe JSON>'Only proceed to implementation when ValidationReport.valid is true.
Route automatically with:
scripts/route-mode.mjs --json "<prompt>"
Routing policy:
build-now when prompt contains explicit Dinachi slugs or direct install/add verbs.plan-first when prompt is broad, qualitative, or design-oriented without concrete component selection.plan-first.The plan-first pipeline uses:
IntentEnvelope: { request_id, intents, ambiguities, confidence }GuidanceDecision: { status, reason, question?, options?, candidates? }UIRecipe: { recipe_id, goal, layout, components, actions, bindings, states }ValidationReport: { valid, errors, warnings, fixes }references/components.registry.json as the source of truth for allowed Dinachi slugs and capabilities.build-now) for concrete requests.plan-first) for ambiguous or system-level requests.development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.