185건 · 관련도순
Build scroll animations with GSAP or Framer Motion, including fade-ins, parallax effects that move layers at different speeds, pinned sections, and horizontal scrolling. Provides implementation patterns for vanilla JavaScript, React, and Next.js, with accessibility guidance.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use Mars as a voice partner for reflecting on meaning, identity, and recurring patterns, or demonstrating a personal AI to others. It adapts between reflective conversation and demonstrations that search stored knowledge and summarize shared links.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a Kortix production release from choosing a version and writing release notes to testing on staging, merging the release pull request, and verifying production. Diagnose blocked promotions and direct fixes back to the dev branch.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design web interfaces, build prototypes, and integrate changes into existing apps while respecting their visual rules and components. Choose direct code generation or Claude Code design commands, with an experimental browser canvas option for visual review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review UI animation code for purposeful motion, responsive timing, correct origins, performance, and accessibility. Get a table of specific changes with reasons, followed by an approval or blocking decision ranked by impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and review interface components with guidance on animation timing, press feedback, drag behavior, and accessibility. Decide when motion helps, choose concrete settings, and explain proposed code changes in a before-and-after comparison.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore personal meaning by reflecting on significant experiences, sacrifices, and mortality. Develop a one-sentence statement of what matters, then reconsider how to spend limited time using a monthly question about having one year left.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate beliefs and spiritual claims by asking what evidence could show them to be wrong. Plan personal trials of practices such as meditation, review observed results, and write principles that distinguish evidence from personal experience.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a practice-area guide for a legal clinic that sets intake questions, how much help AI gives students, supervisor review requirements, checks using other plugins, and local rules. The guide configures how student-facing skills behave.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create agency, studio, architecture, or portfolio websites using oversized typography, black-and-white sections, and documentary photography. Arrange project stories and irregular image collages alongside menus and FAQs designed for keyboard, touch, and reduced-motion use.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and refine web interfaces around their audience, tasks, and brand tone. Covers typography, color, layout, motion, accessibility, and performance, with guided techniques for reviewing existing screens and preparing them for release.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps build and review interface details such as button feedback, menus, animations, and drag gestures. Provides concrete implementation guidance based on usage frequency, responsiveness, rendering performance, and accessibility, including when to reduce or omit motion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or revise Beamer slides, a LaTeX presentation format, and compile them into PDFs. Shape each slide around one clear claim, adapt the structure to the audience, and check typography, diagram spacing, and compilation warnings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop features and fix bugs through test-driven development: write a failing test, add minimal code to pass, then clean up. The workflow assigns agents to planning, test writing, implementation, and validation of the full test suite.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, domain-driven-design - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, REMOVE-TECHNICAL-DEBT-PLAN.md) so the journey resumes across sessions. Use when the user wants to tame a legacy codebase, pay down technical debt safely, avoid a big-bang rewrite, or says 'we are afraid to touch this code'. For a fresh vibe-coded prototype, improve-code-quality; for greenfield structure, design-code-architecture; for a product-and-UX pass, improve-app; to optimize a working codebase for speed, architecture-optimization. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app's architecture, choose boundaries and a domain model, decide monolith versus microservices, or says 'how should I structure this app'. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation fits a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code-quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", "strategic design", "the code doesnt match the business", or "how do we split this big system". Also trigger when breaking a monolith into services, defining service boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.