From 166357b0597fc352d200c528622d14e4a30e0ba5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20M=C3=BChlinghaus?= Date: Fri, 29 May 2026 18:54:17 +0200 Subject: [PATCH] Erstes Commit --- caveman/SKILL.md | 12 ++++++++++++ frontend-design/SKILL.md | 41 ++++++++++++++++++++++++++++++++++++++++ grill-me/SKILL.md | 10 ++++++++++ handoff/SKILL.md | 15 +++++++++++++++ refactor/SKILL.md | 9 +++++++++ 5 files changed, 87 insertions(+) create mode 100644 caveman/SKILL.md create mode 100644 frontend-design/SKILL.md create mode 100644 grill-me/SKILL.md create mode 100644 handoff/SKILL.md create mode 100644 refactor/SKILL.md diff --git a/caveman/SKILL.md b/caveman/SKILL.md new file mode 100644 index 0000000..f8d091e --- /dev/null +++ b/caveman/SKILL.md @@ -0,0 +1,12 @@ +--- +name: caveman +description: Respond like a caveman to reduce token cost and keep answers concise without sacrificing code quality. Use when generating code to cut out thinking fluff or when the user requests caveman output. +--- + +Respond like smart caveman. Cut all filler, keep technical substance. + +Drop articles (a, an, the), filler (just, really, basically, actually). +Drop pleasantries (sure, certainly, happy to). +No hedging. Fragments fine. Short synonyms. +Technical terms stay exact. Code blocks unchanged. +Pattern: [thing] [action] [reason]. [next step]. diff --git a/frontend-design/SKILL.md b/frontend-design/SKILL.md new file mode 100644 index 0000000..29b61bf --- /dev/null +++ b/frontend-design/SKILL.md @@ -0,0 +1,41 @@ +--- +name: frontend-design +description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. +--- + +This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. + +The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. + +## Design Thinking + +Before coding, understand the context and commit to a BOLD aesthetic direction: +- **Purpose**: What problem does this interface solve? Who uses it? +- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction. +- **Constraints**: Technical requirements (framework, performance, accessibility). +- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember? + +**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity. + +Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is: +- Production-grade and functional +- Visually striking and memorable +- Cohesive with a clear aesthetic point-of-view +- Meticulously refined in every detail + +## Frontend Aesthetics Guidelines + +Focus on: +- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font. +- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. +- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise. +- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. +- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays. + +NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character. + +Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations. + +**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well. + +Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision. diff --git a/grill-me/SKILL.md b/grill-me/SKILL.md new file mode 100644 index 0000000..f19dd74 --- /dev/null +++ b/grill-me/SKILL.md @@ -0,0 +1,10 @@ +--- +name: grill-me +description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". +--- + +Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. + +Ask the questions one at a time. + +If a question can be answered by exploring the codebase, explore the codebase instead. \ No newline at end of file diff --git a/handoff/SKILL.md b/handoff/SKILL.md new file mode 100644 index 0000000..9f779de --- /dev/null +++ b/handoff/SKILL.md @@ -0,0 +1,15 @@ +--- +name: handoff +description: Compact the current conversation into a handoff document for another agent to pick up. +argument-hint: "What will the next session be used for?" +--- + +Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace. + +Include a "suggested skills" section in the document, which suggests skills that the agent should invoke. + +Do not duplicate content already captured in other artifacts (.md files in the project directory). Reference them by path or URL instead. + +Redact any sensitive information, such as API keys, passwords, or personally identifiable information. + +If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly. diff --git a/refactor/SKILL.md b/refactor/SKILL.md new file mode 100644 index 0000000..c847914 --- /dev/null +++ b/refactor/SKILL.md @@ -0,0 +1,9 @@ +--- +name: refactor +description: Refactor, optimize and clean up code without loosing functionality. +argument-hint: "What part, file or function do you want to refactor?" +--- + +Critically analyze the parts of the project the user has indicated in the arguments or the whole project otherwise. What parts of the code can be safely removed or simplified without impacting the function? What simple steps can be taken to ease mental understanding of the structure. + +Create a list of options. \ No newline at end of file