design-qa-dev-prep
Skill0 starsChanged 35 days agoNo licenceView on GitHub
Checks the designers' inner-page templates against the page-type design briefs, the reference kit and the written pages before dev handoff, and writes dev's asset checklist. Reads the templates from Figma through the Figma connector, or from a design inventory the designer fills in; a script checks that every brief section has a container and none is empty, the template holds the longest page, CTAs sit where the brief puts them, colours and fonts match the brand kit and every asset has its details. Writes design/slug/slug-design-qa-devprep.md ending in RESULT PASS or FAIL. Use when Design asks for the design quality checklist, design QA or dev prep on the page templates, or whether the inner-page templates fit the pages and are ready for development. Do NOT use for template briefs (use page-type-design-briefs), the homepage brief (use homepage-design-brief), the dev handoff index (use dev-handoff-index), staging or live site checks (use technical-seo-checker), or the kit (use client-reference-kit).
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- blueprint-deckSkill
- case-studySkill
- clickup-progress-syncSkill
- client-context-updateSkill
- client-feedbackSkill
- client-reference-kitSkill
- competitor-analysisSkill
- content-briefSkill
- content-gap-analysisSkill
- content-quality-auditorSkill
- dev-handoff-indexSkill
- google-ads-analysisSkill
- google-ads-auditSkill
- growth-blueprintSkill
- homepage-design-briefSkill
- keyword-researchSkill
- kickoff-call-briefSkill
- kickoff-call-processingSkill
- new-build-kickoffSkill
- offsite-signal-analyzerSkill
- page-type-design-briefsSkill
- project-close-outSkill
- prospect-digital-auditSkill
- retainer-roadmapSkill
- seo-content-writerSkill
- seo-drift-monitorSkill
- serp-analysisSkill
- site-structure-optimizerSkill
- staging-site-qaSkill
- subagent-performance-reviewSkill
- technical-seo-checkerSkill
- week-1-client-emailSkill
- week-1-handoff-checkSkill
- week-2-client-emailSkill
- week-2-handoff-checkSkill
- week-5-client-emailSkill
- week-5-handoff-checkSkill
- week-6-go-live-emailSkill
- welcome-emailSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.