Build Great Things

Guides phased design and build of websites and web applications with quality checklists.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill build-great-things-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Build Great Things
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/build-great-things
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill build-great-things-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated websites and web apps often look generic, skip polish phases, and ship with disconnected layers, missing edge states, and flat interactions. This Skill provides a structured six-phase build playbook that enforces intentional design decisions from brand foundation through launch. ## Core Features & Use Cases - Phased Build Sequence: Six ordered phases (Foundation, Structure, Craft, Motion & Interaction, Performance & Polish, Launch & Growth) for both marketing websites and complex web applications, with a routing table mapping tasks to the right reference file. - Mandatory Quality Checklist: Pre-ship verification covering states, interaction feedback, visual craft, responsiveness, performance, accessibility, and structural coherence between frontend, API, and database layers. - Design Philosophy Grounding: Applies Ousterhout's complexity management, Refactoring UI's constraint-based design, and surface alignment principles, with links to deep research papers per phase. - Use Case: When a user says a page looks "generic" or "needs more polish", the Skill routes to the Craft and Motion references to systematically fix typography, spacing scales, hover states, and scroll animations. ## Quick Start Ask the agent to build a new landing page for your product and it will follow the phased sequence starting from brand foundation through launch-ready polish.

Frequently Asked Questions about Build Great Things

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a website from scratch with this skill?▼

Start with the Foundation phase covering brand identity, positioning, and information architecture, then proceed through Structure, Craft, Motion, Performance, and Launch phases in order. The routing table in SKILL.md maps each task to the correct reference file under references/website/.

How to fix a UI that looks generic or amateur?▼

Read the Craft and Motion & Interaction references, which cover curated color palettes, typeface pairing, geometric spacing scales, hover effects, and scroll animations. The skill also lists 13 common AI laziness patterns, such as default Tailwind colors and arbitrary spacing, to actively avoid.

What is the difference between the website and webapp tracks?▼

The website track targets marketing pages, landing pages, and content sites with emphasis on conversion and SEO. The webapp track targets data-dense, state-heavy applications, adding state architecture, form design, data visualization, drag-and-drop, and onboarding flows.

Does this skill cover accessibility and performance requirements?▼

Yes, the Performance & Polish phase and quality checklist require WCAG AA contrast, semantic HTML, keyboard navigation, reduced-motion support, Core Web Vitals targets (LCP under 2.5s, INP under 200ms, CLS under 0.1), and font loading strategies.

What does the structural coherence checklist verify?▼

It verifies that generated artifacts like types and migrations are fresh, API contracts match implementation, database schemas match ORM models, non-public routes require authentication, and integration tests run against real infrastructure rather than mocks.

When should I not skip the motion and polish phases?▼

Never, according to the skill. Phases 04 and 05 are mandatory because they separate functional output from exceptional output, covering micro-interactions, page transitions, loading and empty states, and edge-case handling that users encounter most.