agentleFS
pobstetapobsteta/aigora/.claude/skills/build-website/SKILL.md

build-website

Skill0 starsChanged 45 days agoMITView on GitHub

Build premium static websites using the PRISM framework (6-phase process). Use when asked to build, design, or create a website or landing page. For interactive apps with databases and auth, use build-app instead.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the copy for each section (headlines, body, CTAs)

    line 45
  2. Distinctive:

    Every animation must serve a purpose (guide attention, provide feedback)

    line 74
  3. Distinctive:

    Never animate just because you can

    line 75
  4. Very specific:

    Always provide prefers-reduced-motion fallback

    line 76
  5. Distinctive:

    Add interactions and animations

    line 92
  6. Distinctive:

    Never use stock placeholder content — write real copy or ask for it

    line 109
  7. Distinctive:

    Every section must earn its place — if it doesn't serve the user journey, cut it

    line 110
  8. Distinctive:

    Prefer CSS animations over JS where possible (GPU-accelerated)

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build Website — PRISM Framework

Build premium static websites that look custom-designed, not template-generated.

When to Use

  • Landing pages
  • Portfolio sites
  • Business websites
  • Marketing pages
  • Product launch pages

NOT for: Apps with databases, user auth, dashboards → use build-app instead.

The PRISM Framework

Phase 1: Position

Establish message, audience, and goal clarity before touching code.

Ask the user:

  1. What is this website for? (product, service, portfolio, event)
  2. Who is the primary audience?
  3. What's the single most important action a visitor should take? (CTA)
  4. What tone should it convey? (professional, creative, technical, playful)
  5. Are there any websites you admire or want to reference?

Read: context/my-business.md and context/my-voice.md for brand context.

Output: Clear creative brief with: audience, goal, CTA, tone, references.

Phase 2: Rough

Structure and hierarchy planning. No code yet.

  1. Define the page sections (hero, features, testimonials, CTA, footer)
  2. Write the copy for each section (headlines, body, CTAs)
  3. Plan the visual hierarchy (what draws the eye first, second, third)
  4. Map the user journey (land → scan → engage → convert)

Output: Section-by-section wireframe in markdown with copy.

Phase 3: Identity

Design system definition.

  1. Typography — Choose 2 fonts: heading (personality) + body (readability)
  2. Colors — Primary, secondary, accent. Dark/light modes.
  3. Spacing — Consistent scale (4px base, 8, 16, 24, 32, 48, 64, 96)
  4. Components — Button styles, card styles, section patterns
  5. Design tokens — Define as CSS custom properties

Output: Design system as CSS variables and component specifications.

Phase 4: Sensation

The "wow" layer that separates premium from template.

  1. Micro-interactions — Button hovers, scroll reveals, focus states
  2. Scroll animations — GSAP ScrollTrigger for section entrances
  3. Visual effects — Glassmorphism, gradients, grain textures, shadows
  4. Typography animation — Text reveals, counter animations
  5. Performance budget — Keep FCP under 1.5s, LCP under 2.5s

Rules:

  • Every animation must serve a purpose (guide attention, provide feedback)
  • Never animate just because you can
  • Always provide prefers-reduced-motion fallback

Phase 5: Make

Build the website.

Stack:

  • Astro (static site generator)
  • Tailwind CSS (utility-first styling)
  • GSAP (animations)
  • Vanilla JS (no heavy frameworks for static sites)

Build order:

  1. Scaffold Astro project
  2. Implement design tokens as Tailwind config
  3. Build sections top-to-bottom (hero first)
  4. Add interactions and animations
  5. Responsive design (mobile → tablet → desktop)
  6. Dark mode (if specified)

Phase +Measure

Quality assurance.

  1. Performance — Lighthouse score > 90 on all metrics
  2. Accessibility — WCAG 2.1 AA compliance, keyboard navigation, screen reader testing
  3. SEO — Meta tags, Open Graph, structured data, sitemap
  4. Responsive — Test at 320px, 768px, 1024px, 1440px
  5. Cross-browser — Chrome, Firefox, Safari minimum
  6. CTA effectiveness — Is the primary action obvious and easy?

Rules

  • Never use stock placeholder content — write real copy or ask for it
  • Every section must earn its place — if it doesn't serve the user journey, cut it
  • Mobile-first responsive design
  • Performance is non-negotiable — no heavy libraries for simple effects
  • Prefer CSS animations over JS where possible (GPU-accelerated)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.