marcmarti9/agentit - 2페이지

gsap-performance

Performance rules for GSAP and high-motion web experiences: compositor-friendly properties, batching, quick setters, timeline ownership, ScrollTrigger cost, mobile constraints, cleanup, and runtime profiling.

원문 언어: 영어

gsap-scrolltrigger

Official-GSAP-informed guidance for scroll-triggered and scroll-scrubbed animation: pinning, scrub timelines, parallax, horizontal sections, start/end markers, snapping, refresh behavior, React cleanup, and ScrollTrigger debugging.

원문 언어: 영어

impeccable-design

Craft-first frontend design direction adapted from Impeccable. Use to design, redesign, critique, polish, harden, simplify, typeset, animate, adapt, or push a frontend beyond safe AI defaults across marketing sites and product UI.

원문 언어: 영어

scrollytelling-web

Design and implement cinematic scroll-driven web narratives: pinned scenes, scrubbed timelines, product decomposition, image sequences, section transitions, spatial storytelling, and progressive 3D reveals. Use when scroll itself drives the story.

원문 언어: 영어

threejs-product-storytelling

Premium Three.js / React Three Fiber product visualization for web storytelling: GLB/glTF scene structure, exploded views, camera direction, lighting, materials, scroll coupling, labels, post-processing, responsive degradation, and GPU validation.

원문 언어: 영어

anti-ai-slop-design

Prevent generic AI design slop (purple glows, generic cards, boring typography, lifeless layouts). Enforce brand-authentic visual identity, curated color systems, and responsive typography.

원문 언어: 영어

frontend-ui-engineering

Build accessible responsive interfaces. Use for UI, CSS, components, or layout; not for backend-only work.

원문 언어: 영어

context-engineering

Manage agent context and progressive disclosure. Use for context budgets, memory, or harness setup; not for ordinary coding.

원문 언어: 영어

source-driven-development

Ground implementation in authoritative docs. Use for current frameworks, libraries, or standards; not when local behavior is the only source needed.

원문 언어: 영어

test-driven-development

Drive behavior changes with tests first. Use for new logic, bugs, and regressions; not for explanations or static prose.

원문 언어: 영어

api-and-interface-design

Design stable APIs and module boundaries. Use for public interfaces, REST/GraphQL endpoints, or cross-module contracts; not for ordinary implementation.

원문 언어: 영어

browser-testing-with-devtools

Verify browser behavior with Chrome DevTools. Use for DOM, console, network, performance, or visual checks; not for backend-only work.

원문 언어: 영어

ci-cd-and-automation

Set up CI/CD quality gates. Use for pipelines, test runners, or deployment automation; not for ordinary local tests.

원문 언어: 영어

code-review-and-quality

Review changes for correctness, security, and maintainability. Use before merge or handoff; not for implementing the feature.

원문 언어: 영어

code-simplification

Simplify working code without behavior changes. Use for readability refactors; not for new features or bug diagnosis.

원문 언어: 영어

deprecation-and-migration

Plan safe deprecation and migration. Use when removing or replacing systems/APIs; not for routine schema changes.

원문 언어: 영어

documentation-and-adrs

Record decisions and durable technical context. Use for ADRs, public APIs, or project documentation; not for incidental comments.

원문 언어: 영어

doubt-driven-development

Challenge non-trivial decisions with fresh review. Use for high-stakes or unfamiliar work; not for routine low-risk edits.

원문 언어: 영어

find-skills

Discover reusable skills. Use when looking for an installable capability; not when the required skill is already known.

원문 언어: 영어

git-workflow-and-versioning

Apply Git workflow and versioning conventions. Use for branching, commits, releases, or changelogs; not for code review itself.

원문 언어: 영어

idea-refine

Refine vague ideas into decisions. Use for ideation and assumption stress tests; not for implementation of a settled task.

원문 언어: 영어

incremental-implementation

Deliver multi-file changes in tested slices. Use when implementation spans files or risks growing; not for a one-line edit.

원문 언어: 영어

observability-and-instrumentation

Add logs, metrics, traces, and alerts. Use when production behavior needs evidence; not for ordinary debugging without instrumentation scope.

원문 언어: 영어

performance-optimization

Diagnose and improve performance. Use for measured bottlenecks, load times, queries, or Core Web Vitals; not for unmeasured cleanup.

원문 언어: 영어

security-and-hardening

Harden boundaries and untrusted input. Use for auth, secrets, data, permissions, or integrations; not for unrelated UI styling.

원문 언어: 영어

shipping-and-launch

Prepare staged production launches. Use for rollout, monitoring, rollback, or release readiness; not for local development.

원문 언어: 영어

spec-driven-development

Create a specification before coding. Use for new or ambiguous projects/features; not when the contract is already agreed.

원문 언어: 영어

supabase-postgres-best-practices

Apply PostgreSQL/Supabase guidance. Use for Postgres queries, schema, indexes, or config; not for SQLite or generic frontend work.

원문 언어: 영어