modern-site-engineering
Skill136 starsChanged 5 months agoMITView on GitHub
Integrate systems after frontend direction.
In this repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-audit-websitesSkill
- accessibility-performance-polishSkill
- agent-evaluation-operationsSkill
- agent-memory-provenanceSkill
- agent-orchestration-architectureSkill
- animation-easing-languageSkill
- animation-jank-qaSkill
- animation-tool-routerSkill
- anti-generic-website-reviewSkill
- brand-voice-to-ui-copySkill
- browser-inspection-workflowSkill
- code-change-safety-checkpointSkill
- code-change-undo-revertSkill
- color-material-lighting-directionSkill
- content-pruning-reviewSkill
- content-structure-information-architectureSkill
- conversion-forms-checkout-polishSkill
- creativitySkill
- critical-thinkingSkill
- cross-browser-qaSkill
- css-grid-editorial-systemsSkill
- cta-language-systemsSkill
- deep-researchSkill
- design-motion-principlesSkill
- editorial-typography-systemsSkill
- evidence-reconciliationSkill
- final-client-handoffSkill
- frontend-quality-auditorSkill
- frontend-tooling-trust-gateSkill
- gsap-performanceSkill
- hero-image-art-directionSkill
- image-crop-responsive-qaSkill
- image-video-loading-qaSkill
- logical-thinkingSkill
- mobile-responsive-qaSkill
- motion-language-directorSkill
- motion-performance-qaSkill
- motion-react-layout-transitionsSkill
- motion-react-microinteractionsSkill
- motion-react-page-transitionsSkill
- motion-react-patternsSkill
- nextjs-app-router-routingSkill
- nextjs-server-client-boundariesSkill
- nextjs-site-architectureSkill
- non-generic-web-copySkill
- performance-audit-websitesSkill
- performance-budget-labSkill
- premium-visual-reference-librarySkill
- premium-web-build-gateSkill
- radix-accessible-primitivesSkill
- react-accessible-componentsSkill
- react-component-compositionSkill
- react-component-craftSkill
- react-error-loading-empty-statesSkill
- react-form-patternsSkill
- react-responsive-componentsSkill
- react-state-and-effects-disciplineSkill
- reduced-motion-designSkill
- responsive-visual-polish-qaSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Run the app locally when possible.
- Very specific: line 38
Run available lint/build/test commands.
- Very specific: line 43
Prefer section components with clear names: Hero, FeaturedWork, Experience, Gallery, Offer, Journal, Contact.
- Distinctive: line 44
Keep layout primitives minimal and reusable.
- Very specific: line 45
Use responsive constraints: clamp(), minmax(), aspect-ratio, stable grid tracks.
- Distinctive: line 46
Avoid text overflow by designing for the longest realistic labels.
- Distinctive: line 48
Use semantic HTML and accessible labels.
- Distinctive: line 53
Use CSS transitions for tiny state changes.
- Very specific: line 55
Read references/stack-recipes.md when starting a new project or adding dependencies.
≈ “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.
Files
Modern Site Engineering
Operating Mode
Inspect relevant structure, framework, entry files, styling and interaction systems, and available build commands. Proceed within existing authorization and explain material choices.
Selected stack
Retain the selected framework and existing package manager. For a new project with an unresolved choice, use route-enterprise-web-stack if installed. Otherwise, compare the actual rendering, interaction, hosting and maintenance requirements, and choose the smallest compatible stack. Select only dependencies required by the actual components. The roles below are optional capabilities, not an installation list.
Dependency Roles
- Next.js: routing, metadata, optimized images/fonts, production build.
- TypeScript: stable component contracts.
- Tailwind: fast design-system implementation with custom tokens.
- CSS variables: brand colors, spacing, shadows, easing, radii, typography.
- Motion: React-native UI motion, enter/exit, hover/tap, layout transitions.
- GSAP: timeline-driven cinematic sequences, ScrollTrigger, pinned scenes, split text, advanced scroll choreography.
- Lenis: smooth scrolling when the design calls for cinematic scroll.
- Three.js/R3F/Drei: immersive product, material, shader, or spatial scenes.
- lucide-react: icons for controls and clear commands.
- shadcn/ui: accessible component source to customize, not a default visual identity.
- Playwright: visual and interaction verification.
Build Workflow
- Inspect project and commands.
- Reuse the approved visual system; establish type, color, spacing, media and motion only when those decisions are in scope.
- Build version 1 with real content structure.
- Run the app locally when possible.
- Inspect changed visual output in the browser at the requested supported sizes.
- Correct observed spacing, type, hierarchy, interaction, motion or responsive defects on affected surfaces. Repeat checks after edits or unresolved findings, not by fixed cycle.
- Run available lint/build/test commands.
- Report files changed, commands run, and any errors honestly.
Component Defaults
- Prefer section components with clear names:
Hero,FeaturedWork,Experience,Gallery,Offer,Journal,Contact. - Keep layout primitives minimal and reusable.
- Use responsive constraints:
clamp(),minmax(),aspect-ratio, stable grid tracks. - Avoid text overflow by designing for the longest realistic labels.
- Make buttons feel designed: icon placement, focus state, hover state, disabled state.
- Use semantic HTML and accessible labels.
- Respect
prefers-reduced-motion.
Motion Defaults
Use CSS transitions for tiny state changes. Use Motion for component/state animation. Use GSAP only when timeline control or scroll choreography is actually needed. Use Three/R3F only when visual concept benefits from spatial or material interaction.
Read references/stack-recipes.md when starting a new project or adding dependencies.
Ownership
Coordinate integration once framework and direction are chosen. The optional architecture specialist is useful only for an unresolved decision; its absence does not block the local procedure above. A localized task goes directly to its implementation owner; this skill does not require a new site blueprint or full tool stack.
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.

