All authors
Claude Skills by ed3dai
github.com/ed3dai41 skills3 installs118 views
- Using Generic AgentsUse to decide what kind of generic agent you should useVotes: 0GitHub stars: 250
- Doing A Simple Two Stage FanoutUse when analyzing a large corpus of text, code, or data that exceeds a single agent's effective context - orchestrates parallel Worker subagents, Critic review subagents, and a final Summarizer subagent with task tracking and failure recoveryVotes: 0GitHub stars: 250
- Creating An AgentUse when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agentsVotes: 0GitHub stars: 250
- Maintaining A MarketplaceUse when creating, releasing, or maintaining a Claude Code Plugin Marketplace - covers marketplace.json schema, version management, release checklists, changelog conventions, and validation to prevent sync drift between plugin.json and marketplace.jsonVotes: 0GitHub stars: 250
- Maintaining Project ContextUse when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updatesVotes: 0GitHub stars: 250
- Prompt Security HardeningUse when writing skills, CLAUDE.md files, agent prompts, or any directives that involve shell commands, environment variables, API credentials, file creation, or git operations - prevents secrets leakage into LLM context, unsafe shell patterns, and credential exposureVotes: 0GitHub stars: 250
- Testing Skills With SubagentsUse when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholesVotes: 0GitHub stars: 250
- Writing Claude DirectivesUse when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers token efficiency, compliance techniques, and discovery optimization.Votes: 0GitHub stars: 250
- Writing Claude Md FilesUse when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness datesVotes: 0GitHub stars: 250
- Writing SkillsUse when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalizationVotes: 0GitHub stars: 250
- Coding EffectivelyALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.Votes: 0GitHub stars: 250
- Defense In DepthUse when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixedVotes: 0GitHub stars: 250
- Howto Code In RustUse when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organizationVotes: 0GitHub stars: 250
- Howto Code In TypescriptUse when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions - comprehensive house style covering type vs interface rules, function declarations, FCIS integration, immutability patterns, and type safety enforcementVotes: 0GitHub stars: 250
- Howto Develop With PostgresUse when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write separation, type safety for UUIDs/JSONB, and snake_case conventions to prevent data corruption and type errorsVotes: 0GitHub stars: 250
- Howto Functional Vs ImperativeUse when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern with mandatory file classificationVotes: 0GitHub stars: 250
- Programming In ReactUse when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript, hooks usage, component composition, and common pitfalls to avoidVotes: 0GitHub stars: 250
- Property Based TestingUse when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testingVotes: 0GitHub stars: 250
- Writing For A Technical AudienceUse when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticityVotes: 0GitHub stars: 250
- Writing Good TestsUse when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolationVotes: 0GitHub stars: 250
- Asking Clarifying QuestionsUse after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope boundaries, and verifies assumptions to prevent building the wrong solutionVotes: 0GitHub stars: 250
- BrainstormingUse when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validationVotes: 0GitHub stars: 250
- Executing An Implementation PlanUse when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usageVotes: 0GitHub stars: 250
- Finishing A Development BranchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupVotes: 0GitHub stars: 250
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero issuesVotes: 0GitHub stars: 250
- Starting A Design PlanUse when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documentsVotes: 0GitHub stars: 250
- Starting An Implementation PlanUse when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary contextVotes: 0GitHub stars: 250
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutionsVotes: 0GitHub stars: 250
- Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure firstVotes: 0GitHub stars: 250
- 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: 250
- Using Plan And ExecuteUse when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating task todos for checklistsVotes: 0GitHub stars: 250
- Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysVotes: 0GitHub stars: 250
- Writing Design PlansUse after brainstorming completes - writes validated designs to docs/design-plans/ with structured format and discrete implementation phases required for creating detailed implementation plansVotes: 0GitHub stars: 250
- Writing Implementation PlansUse when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledgeVotes: 0GitHub stars: 250
- Playwright DebuggingUse when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issuesVotes: 0GitHub stars: 250
- Playwright PatternsUse when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakinessVotes: 0GitHub stars: 250
- Investigating A CodebaseUse when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in realityVotes: 0GitHub stars: 250
- Researching On The InternetUse when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisionsVotes: 0GitHub stars: 250
- Export Session As MarkdownUse when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocksVotes: 0GitHub stars: 250
- Review Recent SessionsUse when the user wants to review their recent Claude Code sessions for patterns — analyzes the last N sessions (default 5) in the current project, dispatching parallel reviewers per session, then synthesizing cross-session findingsVotes: 0GitHub stars: 250
- Review SessionUse when the user wants to review a Claude Code session for quality — analyzes the current session (or a specified transcript path) for prompting effectiveness, agent performance, and environment gaps, producing actionable recommendationsVotes: 0GitHub stars: 250