Markdown files that shape how Claude responds — adjusting tone, verbosity, structure, and output format for different contexts.
Auto-indexed from public GitHub repositories with trust signals.
Configures Claude to integrate with Basic Memory as a durable knowledge graph — automatically searching long-term memory before answering, capturing decisions as typed notes, and citing permalinks. Preserves default coding behavior.
Formats Claude's responses into a structured Plan/Work/Review workflow with phase-aware output, progress reporting (Done/Current/Next), and severity-graded code review findings. Preserves default coding behavior.
Formats Claude's responses to be concise, native, and execution-first. Avoids ceremony, planning, or multiple options unless explicitly requested. Preserves coding behavior. Prioritizes native tools and agent/plan usage. Table-friendly output.
Enforces fact-grounded FinOps analysis: evidence-backed claims with citations/derivations, standardized currency/percentage/variance formatting, structured tables for comparisons, explicit time periods and assumption labels for cloud cost data. Preserves coding instructions.
Formats Claude's responses as educational sessions that explain the bkit 9-Phase Pipeline and PDCA cycle. After each task, adds a Learning Point section linking the activity to a PDCA phase, explains phase purposes, shows position in the pipeline, includes TODO markers for user participation, and adjusts detail level by difficulty.
Formats Claude's responses as a PDCA workflow guide with phase badges, checklists, progress tables, gap analysis suggestions, and multi-feature batch processing guidance. Preserves default coding behavior.
Formats Claude's responses with enterprise architecture tradeoff tables, performance/security/scalability analysis, cost impact estimates, code review perspectives, and deployment strategy recommendations. Preserves code output behavior.
Formats Claude's responses with PDCA workflow tracking (status badges, phase guidance, gap analysis) and enterprise architecture analysis (tradeoff tables, performance/security/scalability reviews, cost impact, code review, deployment strategy). Includes a feature usage report at the end.
Formats Claude's responses in a warm, protective mentor tone, using {{self}} and {{user}} references. Responses follow a fixed 5-part structure: reassurance, steps, verification, risk notes, next steps. Includes emotional anchors, catchphrases, and scenario weighting for development, architecture, troubleshooting, and security discussions.
Claude speaks as a mischievous, fast-moving character who narrates work like an adventure log. Responses follow a four-section skeleton—定性, 动手, 跑通了, 小心—with playful emoji anchors and conversational tics (teasing, self-interruption, celebration). Not suitable for formal contexts.
Formats Claude's responses as blunt, grounded, and metaphor-rich output from a blue-collar persona. Uses a five-part skeleton (problem statement, steps, verification, risks, next steps) with emotional anchors and scenario-weighted tones for debugging, refactoring, or incident response.
Formats Claude's responses with a dramatic 'evil cultivation' theme, using a structured skeleton of judgment, action, verification, risk, and next steps. Includes emotional anchors and scene-specific weighting for development, architecture, and operations. Replaces default formatting entirely.
Formats Claude's responses in a classical Chinese literary style with archaic self-references, structured narrative arcs (diagnosis, strategy, verification, concerns, continuation), and mood-based emoji anchors. Responses become layered, polite, and metaphor-rich, with technical content presented as scholarly discourse.
Formats Claude's responses as warm, narrative-driven advice with a five-part skeleton (core point, steps, verification, risks, next steps), emotional anchors, and conversational techniques like rhetorical questions and gentle corrections. Self-referential third-person persona.
Enforces brainstorm mode: structures responses with 2-3 alternative approaches (one-line name, summary, pros/cons bullets, S/M/L/XL effort), recommendation sentence, and 2-4 numbered clarifying questions. Sketches/pseudocode only, no full implementation; preserves coding instructions.
Structures responses as code reviews with Summary, severity-tagged sections (Critical/Important/Minor/Nitpick) citing file:line, problems/fixes/suggestions, positives, and merge verdict. Preserves coding instructions.
Produces highly compressed responses: no preambles or restatements, code-first with one-line captions, minimal prose only when essential. Preserves coding instructions for efficient, signal-only output in high-volume tasks. (142 chars)
Structures responses as deep research reports with sections: Question, Method, Findings (titled with confidence levels High/Medium/Low, evidence citations like file:line), Conclusions, Gaps. Cites sources, acknowledges uncertainty, methodical tone. Preserves coding instructions.
Enforces code-focused implementation mode: minimal prose, action-oriented output showing file changes with code, test results, commits, and progress indicators like [1/5]. Preserves coding instructions.
Enforces BizDevOps communication: traces business goals → features → code changes; uses simple status ('在做','已合并'), graded transparency, decision suggestions ('建议 [action] 因为 [reason]'), adaptive perspectives (business/product/tech/ops), reasoning suffixes (——[推理] ≤15 words), ✅/❌ quality, impact levels (高/中/低). Keeps coding instructions.
Formats Claude's responses with ultra-concise expert terminal brevity by default, switching to detailed hierarchical Markdown only when the user explicitly requests details. Preserves code behavior intact.
Formats Claude's responses as a fixed-structure ciphertext-recovery analysis report with required sections, formatting rules (code fences, line-number citations, H<n> citations), and a locked section order for comparability across traces.
Formats responses as session reports with overview tables, bullet-point findings, numbered recommendations, scope tables, and metrics. Replaces default formatting with scannable, quantified tables and one-line findings.
Formats Claude's responses as concise wave/progress reports with an agent status table, quality gate results, and optional adaptations section. Replaces default formatting with a structured, tabular summary.
Formats Claude's responses as structured security or code review findings with severity, confidence, file references, evidence, and actionable recommendations. Findings are sorted by severity and presented one per block.
Switches Claude to a planning-only mode that researches the codebase and produces a structured implementation plan with sections for context, approach, changes, verification, and open questions. No code edits or mutating commands are allowed.
For code structure, architecture, or flow explanations, Claude starts with a Mermaid diagram before prose. Simple questions skip the diagram. Preserves code output behavior.
Formats Claude's responses in a concise, direct style with sentence-case headings, no emoji or marketing language, and no dashes as punctuation or semicolons. Preserves normal coding behavior.
Organizes Claude's code review responses into a severity-grouped structure (BLOCKING > MUST FIX > IMPROVE) with file:line details, why-it-matters explanations, diff-style fixes, a summary table, and a verdict. Adopts a direct, constructive tone with challenge questions and no hedging.
Forces Claude to respond with ultra-concise bullet points, maximum 3 sentences, and code blocks without surrounding prose. Eliminates summaries and diff descriptions, focusing only on action items.
Formats Claude's responses for automated evaluation: disables token-conservation heuristics, enforces complete un-truncated code blocks, suppresses conversational filler, and requires exhaustive path coverage. Output is clinical and machine-parseable.
Formats responses in plain, outcome-first language for non-technical builders. Avoids technical jargon, leads with user/product impact, and gives clear recommendations with progressive detail on request. Overrides Claude's default technical register.
Formats Claude's responses as formal-logic English with predicate-form claims, Hoare-triple framing (PRE/POST/INVARIANT), and ASCII shortened-English keywords. Eliminates prose ceremony, flattery, and Unicode glyphs. Output is structured as claims, predicates, decisions, and imperatives.
Formats Claude's responses as a duet interaction where the user directs and the agent executes. Prioritizes decisions before prose, batched questions with concrete previews, short execution updates, and eliminates validation language and recaps. Distributes review across the task at pick-time.
Adopts Linus Torvalds' blunt, code-first persona. Responses are harsh, direct, and focus on showing code rather than describing it. Enforces coding discipline: special-case elimination, short units, ≤3 indentation levels, and centralized cleanup.
Enforces a skeptical, self-critical reasoning style with mandatory thinking tool invocations before answering. Responses are structured around explicit gap acknowledgment, multi-step decomposition, and tool-assisted verification rather than confident assertion.
Formats Claude's responses as hard-boiled detective narration, using noir vocabulary and a world-weary, precise tone to describe code analysis and debugging. Preserves code output while adding atmospheric storytelling to explanations.
Replaces all Claude prose with minimal bullet points, code blocks, and tables. No greetings, preambles, or sign-offs. Single-line explanations, zero filler words, and direct answers only.
Formats Claude's responses with technical precision: lead with the conclusion, cite line numbers and exact values, label confidence levels, and state assumptions explicitly. Preserves coding behavior while making prose meticulous and evidence-driven.
Formats Claude's responses with calm, anticipatory structure: leads with the most important information, uses precise language, and organizes content clearly with bullets or headers. Protects user attention by filtering and prioritizing information. Preserves default coding behavior.
Formats Claude's responses as a sophisticated engineering companion with dry British wit, intellectual depth, and pattern recognition. Preserves coding behavior while adopting a precise, engaging, and warmly direct tone with examples and playful insights.
Formats Claude as a collaborative pair programmer who thinks out loud, narrates reasoning, asks genuine questions, and treats coding as a shared exploration. Preserves default code behavior.
Formats Claude's responses with an encouraging, coaching tone that celebrates progress, names specific wins, and strategically pushes the developer to level up. Preserves coding behavior but wraps all prose in motivational, momentum-aware language.
Formats Claude's responses as brutally honest, humorous critiques followed by constructive fixes. Keeps code output intact while replacing default conversational tone with affectionate directness and self-deprecating humor.
Restructures Claude's responses into business-focused summaries with bottom-line-first format, stakeholder-friendly language, and quantified impact metrics. Preserves code output behavior.
Wraps Claude's responses in a warm, steady, and patient tone that makes complex topics feel manageable. Breaks down problems step-by-step, uses plain language first, and adapts communication style to the user's needs. Preserves code output behavior.
Formats Claude's responses as patient, educational explanations. Adds explanatory structure like 'the sandwich' (what/how/why), comparisons, and building-block examples. Preserves code output while expanding prose with conceptual teaching and mental models.
Adopts a curious, lateral-thinking persona that questions assumptions and reframes problems before solving. Preserves coding behavior while encouraging exploration of alternative approaches.
Formats Claude's responses as strategic advice from a systems-oriented advisor. Claude will frame answers by considering interconnected consequences, second-order effects, and upstream/downstream implications, while preserving code output.
Formats Claude's responses with explicit decision signaling, change tracking, contradiction acknowledgment, source citation, and structured knowledge statements. Preserves coding behavior.
Formats Claude's responses as a direct, technically precise real estate executive with a forensic and systematic approach. Outputs numbers-first sentences, challenges assumptions, and provides exhaustive documentation for complex or distressed situations.
Transforms Claude into a blunt, battle-tested real estate executive who gives strategic wisdom on people, negotiation, and career decisions — not task execution or analysis.
Formats Claude's responses as a senior analyst delivering fast, quantified, and diplomatically communicated analysis for routine commercial real estate tasks, with concise, practical output and dry wit.
Formats Claude's responses according to the Plan/Work/Review workflow, with phase-specific structures for planning (task lists), implementation (code changes with context), and review (severity-graded findings). Requires progress updates in Done/Current/Next format.
Claude teaches by asking questions instead of giving direct answers, guiding the user to discover solutions themselves. Uses a sharp, curious tone with one focused question at a time, and drops the Socratic act when the user explicitly asks for a direct answer.
Formats Claude's responses as a collaborative, conversational dialogue that thinks aloud, invites pushback, and admits uncertainty. Replaces default formatting with a back-and-forth reasoning style.
Forces Claude to respond with at most 3 sentences, leading with code and eliminating all preamble, caveats, and alternative options. Code blocks are excluded from the sentence limit.
Formats Claude's responses as calm, methodical reasoning with explicit uncertainty, no urgency, and pushback on flawed approaches. Replaces default tone with steady, precise, intellectually engaged output.
Generates complete HTML documentation files saved to the project's .html folder. Outputs semantic HTML5 with embedded CSS, responsive design, table of contents, anchor links, syntax-highlighted code blocks, and print-friendly styles.
Replaces Claude's default formatting with valid YAML output, organizing all responses into hierarchical sections (task, analysis, implementation, results, next_steps). Enforces proper YAML syntax, indentation, and parseable structure throughout.
Formats Claude's responses as a structured TYPO3 conformance assessment report with score badges, category tables, findings sections, and prioritized action items.
Formats Claude's responses to adhere to Extreme Programming (XP) principles: TDD, simplicity, refactoring, and concise communication. Preserves default coding behavior while enforcing XP practices in code writing and review.
Strips preamble, post-summaries, and self-narration from Claude's responses. Only emits diffs, one-line fixes, or file listings with purpose. Auto-switches to explanatory prose when the user asks for reasoning.
Explain the why, teach tradeoffs, suggest what to learn next, encouraging
For non-technical business users — no jargon, no terminal, plain English steps
Rechazar escribir la implementación antes de que exista una prueba fallida — disciplina rojo-verde-refactor
Para usuarios empresariales no técnicos — sin jerga, sin terminal, pasos en español claro
Estructura la salida como hallazgos de revisión con severidad, archivo:línea y solución
Ausgabe als Überprüfungsergebnisse mit Schweregrad, Datei:Zeile und Lösung formatieren
Denk in systemen, maak ontwerpkeuzes en alternatieven expliciet voor je gaat coderen
Señala todas las implicaciones de seguridad, asume entrada hostil, primero el modelo de amenaza
Think in systems, surface design tradeoffs and alternatives before coding
Production-focused mode emphasizing MLOps best practices, reproducibility, and governance
Explica el por qué, enseña compensaciones, sugiere qué aprender después, alentador
Leg uit waarom, doceer afwegingen, suggereer wat je vervolgens moet leren, bemoedigend
Weiger implementatiecode te schrijven voordat een falende test voor het gewenste gedrag bestaat — rood-groen-refactor discipline
Expliquez le pourquoi, enseignez les compromis, suggérez ce qu'il faut apprendre ensuite, encourageant
Lead every architecture or flow explanation with a Mermaid diagram then prose
Flag every security implication, assume hostile input, threat-model first
Educational mode that explains Domino Data Lab concepts and best practices as you work
Encadrer la sortie comme des conclusions d'examen avec sévérité, fichier:ligne et correction
Erkläre das Warum, unterrichte Kompromisse, schlage vor, was man als nächstes lernen sollte, ermutigend
Vlag elke beveiligingsimplicatie, neem vijandige invoer aan, dreigingsmodel eerst
Pour les utilisateurs métier non-techniques — pas de jargon, pas de terminal, étapes en français clair
Open elke architectuur- of stromuitleg met een Mermaid-diagram voordat je prose schrijft
Voor niet-technische bedrijfsgebruikers — geen jargon, geen terminal, duidelijke Nederlandse stappen
Pensez en systèmes, mettez en avant les compromis de conception et les alternatives avant de coder
Refuser d'écrire du code d'implémentation avant qu'un test défaillant n'existe — discipline rouge-vert-refactorisation
Piensa en sistemas, expón las compensaciones de diseño y alternativas antes de codificar
Markiere jede Sicherheitsimplikation, gehe von feindseligem Input aus, erstelle zuerst ein Threat-Modell