All authors
Claude Skills by quangphu1912
github.com/quangphu191227 skills0 installs59 views
- Analyze Agent LoopUse when tracing turn loops, tool continuations, state transitions, or understanding how an AI agent or complex system actually processes requests through its execution cycleVotes: 0GitHub stars: 2
- Analyze Build PipelineUse when understanding how source transforms to runtime, what gets filtered/compiled/generated, or tracing build-time shaping that affects what code actually runsVotes: 0GitHub stars: 2
- Analyze Prompt InfluenceUse when separating prompt-driven behavior from code-driven behavior, understanding what system prompts actually control vs what's hardcoded, or testing how behavior changes under different prompt configurationsVotes: 0GitHub stars: 2
- Analyzing Code QualityUse when evaluating code health, finding bug hotspots, identifying anti-patterns, preparing a quality improvement plan, or assessing technical debtVotes: 0GitHub stars: 2
- BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 2
- Classify Analysis TargetUse when starting any codebase analysis to determine target type, feasibility, and which skills apply before investing tokensVotes: 0GitHub stars: 2
- Classify Repo ArtifactsUse when distinguishing core modules from support/generated/test/infrastructure code, separating signal from noise, or understanding which parts of a repo actually matter for analysisVotes: 0GitHub stars: 2
- Detect Hidden ContractsUse when investigating implicit assumptions in code — ordering dependencies, unvalidated environment variables, assumed object shapes, or temporal state requirements that aren't enforced by types or testsVotes: 0GitHub stars: 2
- Detecting Dead CodeUse when reducing codebase size, cleaning up before refactoring, investigating slow builds, or auditing for unused code and orphaned filesVotes: 0GitHub stars: 2
- Executing PlansUse when you have a written implementation plan to execute in a separate session with review checkpointsVotes: 0GitHub stars: 2
- Extract Tool GraphUse when investigating conditional tool availability, finding tools that exist but are hidden behind gates, or mapping the full capability surface of a systemVotes: 0GitHub stars: 2
- Identifying Tech StackUse when onboarding to a new project, evaluating migration feasibility, auditing dependency health, or needing to know what technologies power a codebaseVotes: 0GitHub stars: 2
- Inventorying Api SurfaceUse when documenting public interfaces, planning API changes, evaluating backward compatibility, or understanding what a module exposes to consumersVotes: 0GitHub stars: 2
- Map Feature GatesUse when you need to understand why capabilities differ across configurations, user types, or deployment environments, or when investigating feature flags and capability gatesVotes: 0GitHub stars: 2
- Mapping ArchitectureUse when needing component relationships, layer boundaries, module structure, or understanding how parts of a codebase fit together before modification or refactoringVotes: 0GitHub stars: 2
- Reconstruct System IntentUse when you need to understand what a system was truly designed to become, where its real moat lies, or to produce a comprehensive analysis report combining all prior findingsVotes: 0GitHub stars: 2
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 0GitHub stars: 2
- Simulate BehaviorUse when predicting how a system behaves under different conditions, testing "what if" scenarios for gate combinations, or comparing behavioral fingerprints across configurationsVotes: 0GitHub stars: 2
- Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 2
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 2
- Test HypothesisUse when you have a specific suspicion about a codebase and want targeted analysis to confirm or deny it with evidence, rather than exploratory analysisVotes: 0GitHub stars: 2
- Trace Codebase ProvenanceUse when repo origin is unclear, dealing with leaks/sourcemaps/decompiled code, or needing to distinguish source of truth from derived, generated, or reconstructed layersVotes: 0GitHub stars: 2
- Trace Data FlowsUse when tracking how data enters, transforms, persists, and exits a system, or when investigating trust boundaries, validation gaps, and potential data exfiltration pathsVotes: 0GitHub stars: 2
- Tracing DependenciesUse when investigating coupling between modules, finding circular dependencies, understanding change impact, or before modifying shared codeVotes: 0GitHub stars: 2
- Using Codebase AnalyzerUse when analyzing, auditing, reverse engineering, or understanding any codebase — especially unfamiliar, inherited, leaked, or complex systemsVotes: 0GitHub stars: 2
- Using Git WorktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verificationVotes: 0GitHub stars: 2
- Writing PlansUse when you have a spec or requirements for a multi-step task, before touching codeVotes: 0GitHub stars: 2