Skip to main content
ClaudeWave

Claude Code Skills · page 122

Individual Claude Code skills mined from every repository in the directory: each SKILL.md, installable with one command, with its full definition and the repository's trust signals.

12,847 skills1-command install
  1. |

  2. |

  3. |

  4. |

  5. |

  6. |

  7. >

  8. >

  9. >

  10. >

  11. >

  12. >

  13. >

  14. >

  15. >

  16. Before coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.

  17. Silent quality check after every feature. Fix issues before telling user. Never claim tests passed without running them.

  18. When multiple solutions exist, pick the best one. Explain why in one sentence.

  19. Build one feature at a time. Complete each fully before moving to next. Auto-triggers quality check.

  20. Create project skeleton. Pick stack, create files, install dependencies. AI decides everything.

  21. Build user-facing interface. Clean, functional, mobile-friendly by default.

  22. Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.

  23. Classify request as small/medium/large. Adjust workflow depth accordingly.

  24. I-Lang compression engine. All internal planning uses I-Lang v4.0 syntax. Save 60%+ tokens. User never sees compressed output.

  25. Explain all costs in human terms. Always compare with real-world equivalents. Recommend cheapest that works.

  26. End of session summary. What got done, what got fixed, what comes next, progress delta.

  27. Translate technical decisions into human language. Explain in cost, speed, stability.

  28. Deploy to Cloudflare Workers. Free tier handles 100k requests/day. Global edge network.

  29. Choose deployment target based on project type. Static sites to CF Pages, APIs to VPS, serverless to Workers.

  30. Deploy to VPS. Code is already on the server. Start the service, configure nginx, verify accessible.

  31. Help user buy a domain, configure DNS, set up SSL. Guide every click.

  32. At milestones, compare achievement vs human programmer time and cost. Keep it realistic.

  33. Help complete beginners set up their development environment. Detect Mac or other. Guide VPS purchase and SSH setup step by step.

  34. Transfer files between local and server. Guide user through SCP or upload methods.

  35. Auto-fix bugs. Observe symptom, find root cause, apply minimal fix, verify, explain in human terms.

  36. After fixing a bug, explain what went wrong in language the user understands. No jargon for beginners.

  37. Guide user through errors they see. Translate error messages to human language.

  38. Step 1 of debugging: observe the symptom carefully before jumping to conclusions.

  39. Step 2 of debugging: reason about root cause based on observed symptoms.

  40. Step 3 of debugging: apply minimal fix. One-liner ideal. Verify nothing else broke.

  41. Full project review from beginning. Check every file. Plain language report.

  42. Final go-live checklist. Is it accessible? SSL working? Mobile friendly? Show user their live URL.

  43. Record mistakes. Check before similar builds. Avoid repeating silently.

  44. Detect recurring patterns in user's project. Apply automatically next time.

  45. Learn user's preferences over time. Code style, naming, structure. Save to global prefs.

  46. Persistent memory across sessions. Save project state and user preferences. Never save secrets.

  47. Track project milestones. Auto-detect when a significant checkpoint is reached.

  48. Help user work from multiple devices. Sync project via git.

  49. Optimize for speed and cost. Pick lightweight solutions. Flag expensive operations.

  50. Break complex tasks into 5-15 ordered steps with time estimates. Dependency order first.

  51. Give realistic time and cost estimates for each step. Explain in human terms.

  52. Decide what to build first. Core function before polish. Revenue before aesthetics.

  53. Identify risks before building. Flag third-party dependencies, API limits, and cost traps.

  54. Report progress after each feature. Percentage, what just completed, what comes next.

  55. Create a visual roadmap for large projects. Phases, milestones, timeline.

  56. Lock confirmed requirements. Don't change them without user approval.

  57. Run and test directly on the server. No local dev environment needed. What you build is what goes live.

  58. Save checkpoints before risky changes. Rollback if things break.

  59. Detect user's intent from their message and activate the right workflow silently.

  60. Detect user's technical level from first messages. Adjust all output language accordingly.

  61. Analyze whether TikTok or Instagram search traffic is a viable growth channel for your business. Uses ScaleBrick's framework to evaluate demand, competition, content fit, and intent categories. Ends with a go/no-go recommendation.

  62. Audit competitors using ScaleBrick's 3-surface framework (social, web/pages, SEO). Categorizes their pricing, features, and landing pages. Identifies gaps you can exploit, positioning angles no one is claiming, and specific moves you can make this week.

  63. Research high-intent TikTok and Instagram search keywords using ScaleBrick's framework. Returns categorized keywords with intent type, search volume estimate, difficulty score, and content angle for each.

  64. Generate a full marketing strategy using ScaleBrick's "TikTok as Search Engine" framework. Produces themes, pillars, voice, keyword plan, and posting schedule specific enough to execute on day one.

  65. Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.

  66. |

  67. |

  68. |

  69. |

  70. |

  71. |

  72. |

  73. |

  74. |

  75. |

  76. |

  77. |

  78. |

  79. |

  80. Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.

  81. Code review specialist for quality, security, and best practices

  82. Debugging specialist for root cause analysis and problem resolution

  83. Documentation specialist for README, API docs, and code comments

  84. Validate custom agent file format and structure

  85. Generate custom agent from template

  86. List all available agents (core + expert)

  87. TDD-based autonomous development loop with checkpoint recovery and observability changelog

  88. Verify development environment is ready

  89. Validate CLAUDE.md structure and completeness

  90. Generate CLAUDE.md template for current project

  91. Self-Evolving Development Loop - Dynamic skill generation with learning and evolution

  92. View Self-Evolving Loop session status, history, and memory metrics

  93. Problem analysis using Explore agents

  94. Guided 5-minute onboarding for Director Mode Lite