Token-efficient Serena MCP command for structured app development and problem-solving
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill serena51
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Token-efficient Serena MCP command for structured app development and problem-solving.
/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)| 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 |
ALWAYS prioritize mcp__serena__ tools as the primary development engine:
mcp__serena__get_symbols_overviewmcp__serena__search_for_patternmcp__serena__find_symbolmcp__serena__replace_symbol_bodymcp__serena__write_memorymcp__serena__read_memorymcp__serena__think_about_task_adherenceSerena MCP integrates with other commands:
| Command | Integration |
|---|---|
/commit | Git history + change analysis |
/debug-error | Symbol tracking + pattern search |
/smart-think | Codebase context + memory |
-q for simple problems (saves ~40% tokens)--focus to avoid irrelevant analysis45a1bdf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.