Steps
Guide
Write the Skill purpose
Start with a short purpose statement: the Skill creates a footer that is consistent, responsive, and legally complete.
The purpose should be specific enough that the agent does not redesign the footer from scratch on every project.
Connect the Skill to project files
Tell the agent to read the brand asset pack before choosing colors, logos, or visual spacing.
The Skill should define behavior. The files should provide brand-specific values.
Add acceptance checks
Require mobile wrapping checks, keyboard focus checks, contrast checks, and link validation.
The Skill is only complete when the footer works on small screens and all legal links are present.
Be Aware
Stricter the better
Add stricter layout rules and point the Skill to the existing brand files. Avoid reinventing the wheel on brand values or footer structure. The Skill should define rules and checks, not brand-specific values.
Images and other assets
Either provide location with all the images, icons, etc to this skill or add them after creation.
Return to the Main Guide?
Main guide
Reusable Skills: The Website Superpower
Footer Skill Script
Copy / paste
Create a reusable Footer Skill for an AI coding agent.
Goal:
Build a consistent, responsive website footer without redesigning it from scratch for each project.
The Skill must:
- use the project files for brand-specific values such as logo, colors, typography, legal URLs, contact details, and navigation items
- define the footer structure clearly: brand block, navigation group when needed, legal links, optional contact/social links, and copyright line
- use semantic HTML with a footer container
- use nav only for real navigation groups, not for every utility link
- require descriptive link labels
- require responsive behavior so the footer wraps or stacks cleanly on mobile
- require visible keyboard focus on links
- require validation that all required legal links exist and resolve
- require readable color contrast
- require copyright text to stay readable after wrapping
- keep brand-specific values out of the Skill itself when they belong in project files
- stop and ask questions if required inputs are missing instead of inventing values
Output:
1. A Footer Skill specification
2. A checklist for acceptance checks
3. A short list of common failure cases
After each output, ask me:
"Should any instruction in this Footer Skill be updated before we use it again?"
If I answer yes, ask what should change, then rewrite the Skill with the updated instruction included.
If I answer no, keep the Skill as the reusable version for future footer work.