website-creative-direction
Skill1 starsChanged 6 months agoNo licenceView on GitHub
Run a staged creative-direction and build sequence for premium websites, from visual identity through launch audit. Use when the user wants to design, build, or overhaul a website's look, feel, UX flow, or motion system - not for isolated component tweaks. Triggers include "design a website for X", "creative direction for my site", "make my site feel premium/agency-built", "audit my website before launch". Chains 6 stages - creative direction, UX/UI experience map, hero + motion system, build sequence, agency-polish audit, final launch audit. Each stage needs explicit go-ahead before the next starts. Delegates to specialist skills at each stage rather than duplicating their rules - taste-skill for direction, emil-design-eng for motion, impeccable and frontend-design for build/audit, ui-ux-pro-max for pattern lookup. Falls back to inline guidance if a specialist skill isn't installed.
In this repository31 other files it gives its agents.
- anti-sycophancySkill
- blind-spot-auditSkill
- caveman-coworkSkill
- clarifying-questionsSkill
- context-auditSkill
- decision-toolkitSkill
- dispatcherSkill
- earnings-analysisSkill
- fact-checkerSkill
- find-skillsSkill
- frontend-designSkill
- frontend-slidesSkill
- graphifySkill
- handoffSkill
- handover-reviewSkill
- humanizerSkill
- investigateSkill
- llm-councilSkill
- office-hoursSkill
- plan-ceo-reviewSkill
- product-launchSkill
- prompt-masterSkill
- prompt-principlesSkill
- qa-expertSkill
- request-validatorSkill
- retroSkill
- sparring-partnerSkill
- style-enforcer-pipelineSkill
- summarize-docSkill
- task-auditSkill
- usage-local-apiSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
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.