.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/ed3dai/ed3d-plugins
home/skills/ed3dai/ed3d-plugins
ed3dai avatar

ed3dai/ed3d-plugins

42 skills · 727 total installs

View on GitHub
$npx skills add ed3dai/ed3d-plugins
SkillInstalls
asking-clarifying-questionsUse after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope…38playwright-debuggingUse when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation…38researching-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…33using-generic-agentsUse to decide what kind of generic agent you should use27writing-implementation-plansUse when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans…27writing-for-a-technical-audienceUse when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI…25creating-an-agentUse when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt…23coding-effectivelyALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.22brainstormingUse when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured…20howto-code-in-typescriptUse when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions -…20requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles…20executing-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…19investigating-a-codebaseUse when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when…19playwright-patternsUse when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns,…19writing-claude-md-filesUse when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent…19maintaining-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,…18property-based-testingUse when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference…18starting-a-design-planUse when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to…18finishing-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…17programming-in-reactUse when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript,…17systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis,…17test-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…17writing-good-testsUse when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation17writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with…17creating-a-pluginUse when creating a new Claude Code plugin or setting up plugin structure - provides complete file organization, manifest format, and component definitions for…16defense-in-depthUse when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than…16howto-develop-with-postgresUse when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write…16starting-an-implementation-planUse when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context16testing-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…16using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart…16using-plan-and-executeUse when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following…16writing-claude-directivesUse when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts.16verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…15writing-design-plansUse after brainstorming completes - writes validated designs to docs/design-plans/ with structured format and discrete implementation phases required for…15doing-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…12maintaining-a-marketplaceUse when creating, releasing, or maintaining a Claude Code Plugin Marketplace - covers marketplace.json schema, version management, release checklists,…10export-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)…5prompt-security-hardeningUse when writing skills, CLAUDE.md files, agent prompts, or any directives that involve shell commands, environment variables, API credentials, file creation,…5howto-code-in-rustUse when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing…4review-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…4review-sessionUse when the user wants to review a Claude Code session for quality — analyzes the current session (or a specified transcript path) for prompting…4howto-functional-vs-imperativeUse when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell)…—