serena
Token-efficient Serena MCP command for structured app development and problem-solving
Best use case
serena is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Token-efficient Serena MCP command for structured app development and problem-solving
Teams using serena should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/serena/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How serena Compares
| Feature / Agent | serena | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Token-efficient Serena MCP command for structured app development and problem-solving
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Serena: Intelligent App Development Token-efficient Serena MCP command for structured app development and problem-solving. ## Quick Reference ```bash /serena <problem> [options] # Basic usage /serena debug "memory leak in prod" # Debug pattern (5-8 thoughts) /serena design "auth system" # Design pattern (8-12 thoughts) /serena review "optimize this code" # Review pattern (4-7 thoughts) /serena implement "add feature X" # Implementation (6-10 thoughts) ``` ## Options | Option | Description | Example | |--------|-------------|---------| | `-q` | Quick mode (3-5 thoughts) | `/serena "fix button" -q` | | `-d` | Deep mode (10-15 thoughts) | `/serena "architecture design" -d` | | `-c` | Code-focused analysis | `/serena "optimize performance" -c` | | `-s` | Step-by-step implementation | `/serena "build dashboard" -s` | | `-v` | Verbose output | `/serena "debug issue" -v` | | `-r` | Include research phase | `/serena "choose framework" -r` | | `-t` | Create implementation todos | `/serena "new feature" -t` | ## Tool Priorities **ALWAYS prioritize mcp__serena__ tools as the primary development engine:** ### Primary Development Tools (Serena MCP) - **Project Analysis**: Use `mcp__serena__get_symbols_overview` - **Code Search**: Use `mcp__serena__search_for_pattern` - **Symbol Management**: Use `mcp__serena__find_symbol` - **Code Modification**: Use `mcp__serena__replace_symbol_body` ### Memory & Learning - **Knowledge Storage**: Use `mcp__serena__write_memory` - **Experience Retrieval**: Use `mcp__serena__read_memory` - **Progress Tracking**: Use `mcp__serena__think_about_task_adherence` ## Problem-Specific Templates ### Debug Pattern (5-8 thoughts) 1. Symptom analysis & reproduction 2. Error context & environment check 3. Root cause hypothesis generation 4. Evidence gathering & validation 5. Solution design & risk assessment ### Design Pattern (8-12 thoughts) 1. Requirements clarification 2. Constraints & assumptions 3. Architecture options generation 4. Option evaluation (pros/cons) 5. Technology selection 6. Implementation phases ### Implementation Pattern (6-10 thoughts) 1. Feature specification & scope 2. Technical approach selection 3. Component/module design 4. Dependencies & integration 5. Testing strategy ## Cross-Command Integration Serena MCP integrates with other commands: | Command | Integration | |---------|-------------| | `/commit` | Git history + change analysis | | `/debug-error` | Symbol tracking + pattern search | | `/smart-think` | Codebase context + memory | ## Best Practices 1. Start with problem analysis, end with concrete actions 2. Balance depth with token efficiency 3. Use `-q` for simple problems (saves ~40% tokens) 4. Use `--focus` to avoid irrelevant analysis
Related Skills
test
Advanced test implementation command with unit/E2E support, auto-execution, and smart fixing capabilities
project-guidelines-example
Example project-specific skill template based on a real production application.
notion-bug-pr
Skill that pulls bug tickets (titles containing 「不具合」) from a Notion database, investigates root cause in a GitHub repo, applies fixes, and opens draft PRs. Supports three modes — daily recurring schedule, one-shot at a specific time, or immediate on-demand run. Takes three or four args: Notion database URL, repo path or name, and either HH:MM (daily), "once HH:MM" (one-shot), or "now" (immediate).
graphify
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
chrome
Comprehensive Chrome DevTools development system with native Chrome capabilities for debugging, E2E testing, performance analysis, and browser automation
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
tanstack-start
Full-stack React framework powered by TanStack Router with SSR, streaming, server functions, and deployment to any hosting provider.
tanstack-start-server-fn-testing
Unit-test TanStack Start createServerFn handlers via a global vi.mock that combines two patterns from Discussion #2701
tailwind-css-patterns
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.