agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/modern-site-engineering/SKILL.md

modern-site-engineering

Skill136 starsChanged 5 months agoMITView on GitHub

Integrate systems after frontend direction.

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
  1. Distinctive:

    Run the app locally when possible.

    line 35
  2. Very specific:

    Run available lint/build/test commands.

    line 38
  3. Very specific:

    Prefer section components with clear names: Hero, FeaturedWork, Experience, Gallery, Offer, Journal, Contact.

    line 43
  4. Distinctive:

    Keep layout primitives minimal and reusable.

    line 44
  5. Very specific:

    Use responsive constraints: clamp(), minmax(), aspect-ratio, stable grid tracks.

    line 45
  6. Distinctive:

    Avoid text overflow by designing for the longest realistic labels.

    line 46
  7. Distinctive:

    Use semantic HTML and accessible labels.

    line 48
  8. Distinctive:

    Use CSS transitions for tiny state changes.

    line 53
  9. Very specific:

    Read references/stack-recipes.md when starting a new project or adding dependencies.

    line 55

≈ “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

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

  1. Inspect project and commands.
  2. Reuse the approved visual system; establish type, color, spacing, media and motion only when those decisions are in scope.
  3. Build version 1 with real content structure.
  4. Run the app locally when possible.
  5. Inspect changed visual output in the browser at the requested supported sizes.
  6. Correct observed spacing, type, hierarchy, interaction, motion or responsive defects on affected surfaces. Repeat checks after edits or unresolved findings, not by fixed cycle.
  7. Run available lint/build/test commands.
  8. 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.

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.