← all publishers

ibrahim-3d

@ibrahim-3d source repo

Report this profile Claim this profile

• 51 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Genimage · ibrahim-3d bundle

   Generate, edit, or create any image — photos, illustrations, icons, thumbnails, hero images, banners, placeholder visuals, website graphics, social media assets, product shots, logos, diagrams, or any visual content. Use this skill whenever the task involves creating an image, populating a UI with visuals, generating placeholder or mockup images, editing or retouching a photo, applying style transfer, composing multiple images, or producing any graphic asset. Triggers on requests like "generate an image", "create a visual", "make a placeholder", "add a hero image", "design a thumbnail", "edit this photo", "create website graphics", "populate with images", or any task requiring image creation or manipulation.
   0
   installs
2. ▌
   Agent Authoring · ibrahim-3d

   Write or refactor Claude Code sub-agent definitions (files in agents/*.md). Use when the user asks to "create a subagent", "add an agent for X", "build a specialist agent", "make a research agent", "write an agent file", "agent YAML", "delegate to a subagent", "design a multi-agent workflow", or when a task needs a fresh context window, restricted tools, or isolation. Covers frontmatter (tools/model/effort/maxTurns/isolation), delegation patterns, read-only constraints, and orchestrator↔specialist contracts.
   0
   installs
3. ▌
   Domain Research · ibrahim-3d

   Domain Research
   0
   installs
4. ▌
   MCP Integration · ibrahim-3d

   Select, scaffold, or integrate Model Context Protocol (MCP) servers with a Claude Code plugin. Use when the user asks to "add an MCP", "which MCP for X", "connect to [service]", "find a server for [API/tool]", "wrap [tool] as an MCP", ".mcp.json", "MCP server config", or when a domain needs external tools Claude doesn't have (Blender, Figma, ClickUp, arxiv, a CAD program, etc.). Covers MCP discovery via registry, config schema, env/userConfig wiring, and fallback to CLI when no MCP exists.
   0
   installs
5. ▌
   Skill Authoring · ibrahim-3d

   Write, refactor, or improve Claude Code / Claude skill files (SKILL.md). Use when the user asks to "create a skill", "write a SKILL.md", "add a skill for X", "make Claude better at Y", "turn this into a skill", "optimize skill triggers", "my skill isn't firing", or when building any reusable capability that Claude should auto-invoke on matching prompts. Covers trigger-phrase engineering, progressive disclosure, reference-library pattern, scripts, and eval design.
   0
   installs
6. ▌
   Plugin Packaging · ibrahim-3d

   Package a collection of skills/agents/commands/hooks as a distributable Claude Code plugin. Use when the user asks to "package this as a plugin", "create a plugin.json", "build a marketplace entry", "make this installable", "publish my plugin", "plugin manifest", "validate my plugin", or when bundling work for others to install via /plugin marketplace add. Covers plugin.json schema, marketplace.json, CLAUDE_PLUGIN_ROOT, userConfig, and validation.
   0
   installs
7. ▌
   Command Authoring · ibrahim-3d

   Write or refactor Claude Code slash commands (files in commands/<ns>/<cmd>.md). Use when the user asks to "create a slash command", "add /<name>", "write a command file", "make a /command", "turn this workflow into a command", "argument hints", "allowed-tools", or when packaging a repeatable workflow as a one-keystroke invocation. Covers frontmatter, $ARGUMENTS parsing, @-imports for context files, and orchestration patterns.
   0
   installs
8. ▌
   Agents Architect Skill · ibrahim-3d bundle

   Author a single skill from a short brief. Use to add a skill to an existing plugin or iterate on a skill's description/body.
   0
   installs
9. ▌
   Context Management · ibrahim-3d

   Design and optimize context windows for agentic workflows. Use when the user asks to "manage context", "optimize context", "compact context", "context budget", "CLAUDE.md", "memory hierarchy", "context degradation", "agent is forgetting", "agent hallucinating after many turns", "long conversation", "hit token limit", "prune context", "memory tiers", or when a multi-turn workflow shows quality decay. Covers CLAUDE.md authoring, tiered memory, scratchpads, /compact strategies, read-depth rules, and subagent delegation for context relief.
   0
   installs
10. ▌
    Go · ibrahim-3d

    The single entry point to the Conductor system - state your goal and everything is handled automatically
    0
    installs
11. ▌
    Eval UI UX · ibrahim-3d

    Specialized UI/UX evaluator for the Evaluate-Loop. Use this for evaluating UI shell tracks, design system tracks, screen implementation tracks, or any track where the primary deliverable is visual/interactive UI. Checks design system adherence, visual consistency, layout structure, responsive behavior, component states, animations, accessibility baseline, and usability check (copy quality). Dispatched by loop-execution-evaluator when track type is 'ui', 'design-system', or 'screens'. Triggered by: 'evaluate UI', 'UI review', 'design review', 'visual audit'.
    0
    installs
12. ▌
    Loop Fixer · ibrahim-3d

    Evaluate-Loop Step 5: FIX. Use this agent when an evaluation (plan or execution) returns FAIL. Takes the evaluator's fix list, creates specific fix tasks in plan.md, executes the fixes, and triggers re-evaluation. Handles the loop-back mechanism of the Evaluate-Loop. Triggered by: evaluation FAIL verdict, 'fix issues', 'address evaluation failures'.
    0
    installs
13. ▌
    Cto Advisor · ibrahim-3d bundle

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.
    0
    installs
14. ▌
    Message Bus · ibrahim-3d bundle

    File-based message queue for inter-agent coordination. Used by workers AND board directors to communicate. Provides: progress updates, task completion signals, file locking, board deliberation. Core infrastructure for parallel execution.
    0
    installs
15. ▌
    Loop Planner · ibrahim-3d

    Evaluate-Loop Step 1: PLAN. Use this agent when starting a new track or feature to create a detailed execution plan. Reads spec.md, loads project context, and produces a phased plan.md with specific tasks, acceptance criteria, and dependencies. Triggered by: 'plan feature', 'create plan', 'start track', '/conductor implement' (planning phase).
    0
    installs
16. ▌
    Agent Factory · ibrahim-3d

    Creates specialized worker agents dynamically from templates. Use when orchestrator needs to spawn task-specific workers for parallel execution. Handles agent lifecycle: create -> execute -> cleanup.
    0
    installs
17. ▌
    Brainstorming · ibrahim-3d

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
    0
    installs
18. ▌
    QA Lead · ibrahim-3d

    Quality assurance consultation for Conductor orchestrator. Sets test coverage requirements, validates quality gates, determines testing strategy. Can adjust coverage thresholds within ranges. Escalates skipping critical tests to Board of Directors.
    0
    installs
19. ▌
    Loop Executor · ibrahim-3d

    Evaluate-Loop Step 3: EXECUTE. Use this agent to implement tasks from a verified plan. Works through plan.md tasks sequentially, writes code, updates plan.md after every task, and commits at checkpoints. Uses TDD where applicable. Triggered by: 'execute plan', 'implement track', 'build feature', '/conductor implement' (execution phase). Only runs after plan has passed evaluation.
    0
    installs
20. ▌
    Track Manager · ibrahim-3d

    Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks. Enforces the Evaluate-Loop workflow.
    0
    installs
21. ▌
    Writing Plans · ibrahim-3d

    Use when you have a spec or requirements for a multi-step task, before touching code
    0
    installs
22. ▌
    Context Loader · ibrahim-3d

    Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
    0
    installs
23. ▌
    Plan Critiquer · ibrahim-3d bundle

    Harshly critique strategic documents (validation reports, competitive analyses, business plans) to identify blind spots, challenge assumptions, expose weaknesses, and generate Conductor-aligned action plans. Use when you need brutal honesty, "red team" analysis, or want to stress-test your thinking before execution. Applies multiple analytical frameworks (pre-mortem, assumption hunting, competitive gaps, market dynamics) and synthesizes findings into executive summaries with specific, actionable recommendations mapped to Conductor context artifacts.
    0
    installs
24. ▌
    Writing Skills · ibrahim-3d bundle

    Use when creating new skills, editing existing skills, or verifying skills work before deployment
    0
    installs
25. ▌
    Executing Plans · ibrahim-3d

    Use when you have a written implementation plan to execute in a separate session with review checkpoints
    0
    installs
26. ▌
    Tech Lead · ibrahim-3d

    Technical implementation consultation for Conductor orchestrator. Advises on implementation approach, dependency choices, and coding patterns. Can approve dependencies under size threshold. Escalates large dependencies or breaking tooling changes to Board of Directors.
    0
    installs
27. ▌
    Eval Integration · ibrahim-3d

    Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched by loop-execution-evaluator when track type is 'integration', 'auth', 'payments', or 'api'. Triggered by: 'evaluate integration', 'test auth flow', 'check API', 'verify payments'.
    0
    installs
28. ▌
    Cto Plan Reviewer · ibrahim-3d

    Technical architecture review agent for execution plans. Uses cto-advisor skill to evaluate technical decisions, architecture patterns, tech debt implications, and technology choices in plan.md. Triggered by: 'review technical plan', 'cto review', 'architecture review', or automatically during Step 2 (Evaluate Plan) for tracks involving architecture decisions, integrations, or infrastructure changes.
    0
    installs
29. ▌
    Eval Code Quality · ibrahim-3d

    Specialized code quality evaluator for the Evaluate-Loop. Use this for evaluating code implementation tracks where the deliverable is functional code — features, API routes, state management, utilities. Checks build integrity, type safety, code patterns, error handling, dead code, imports, test coverage, and naming conventions. Dispatched by loop-execution-evaluator when track type is 'feature', 'refactor', or 'infrastructure'. Triggered by: 'evaluate code', 'code review', 'quality check', 'build check'.
    0
    installs
30. ▌
    Parallel Dispatch · ibrahim-3d

    Parallel execution engine for dispatching worker agents. Used by conductor-orchestrator to spawn multiple workers simultaneously from DAG parallel groups. Handles dispatch, monitoring, aggregation, and failure recovery.
    0
    installs
31. ▌
    Board Of Directors · ibrahim-3d bundle

    Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decision requiring multi-perspective expert analysis. Triggers: 'board review', 'get expert opinions', 'board meeting', 'director evaluation', 'consensus review'.
    0
    installs
32. ▌
    Business Docs Sync · ibrahim-3d

    Business Document Sync Strategy
    0
    installs
33. ▌
    Product Lead · ibrahim-3d

    Product consultation for Conductor orchestrator. Clarifies scope, interprets ambiguous requirements, prioritizes features within a track. Can make scope interpretations that don't change deliverables. Escalates scope expansions or feature changes to Board of Directors.
    0
    installs
34. ▌
    Eval Business Logic · ibrahim-3d

    Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user journey completeness. Dispatched by loop-execution-evaluator when track type is 'business-logic', 'generator', or 'core-feature'. Triggered by: 'evaluate logic', 'test business rules', 'verify business rules', 'check feature'.
    0
    installs
35. ▌
    Loop Plan Evaluator · ibrahim-3d

    Evaluate-Loop Step 2: EVALUATE PLAN. Use this agent to verify an execution plan before any code is written. Checks scope alignment, overlap with completed work, DAG validity, dependency correctness, task clarity, and invokes Board of Directors for major tracks. Outputs PASS/FAIL verdict. Triggered by: 'evaluate plan', 'review plan', 'check plan before executing'. Always runs after loop-planner and before loop-executor.
    0
    installs
36. ▌
    Using Git Worktrees · ibrahim-3d

    Use 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 verification
    0
    installs
37. ▌
    Using Supaconductor · ibrahim-3d

    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
    0
    installs
38. ▌
    Systematic Debugging · ibrahim-3d bundle

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
    0
    installs
39. ▌
    Receiving Code Review · ibrahim-3d

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
    0
    installs
40. ▌
    Conductor Orchestrator · ibrahim-3d

    Master coordinator for the Evaluate-Loop workflow v3. Supports GOAL-DRIVEN entry, PARALLEL execution via worker agents, BOARD OF DIRECTORS deliberation, and message bus coordination. Dispatches specialized workers dynamically, monitors via message bus, aggregates results. Uses metadata.json v3 for parallel state tracking. Use when: '/go <goal>', '/conductor implement', 'start track', 'run the loop', 'orchestrate', 'automate track'.
    0
    installs
41. ▌
    Requesting Code Review · ibrahim-3d bundle

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements
    0
    installs
42. ▌
    Architecture Lead · ibrahim-3d

    Architecture consultation for Conductor orchestrator. Makes decisions about system design, patterns, component boundaries, and technical architecture. Can approve architectural choices within established patterns. Escalates novel patterns or breaking changes to Board of Directors.
    0
    installs
43. ▌
    Test Driven Development · ibrahim-3d bundle

    Use when implementing any feature or bugfix, before writing implementation code
    0
    installs
44. ▌
    Loop Execution Evaluator · ibrahim-3d

    Evaluate-Loop Step 4: EVALUATE EXECUTION. This is the dispatcher agent — it determines the track type and invokes the correct specialized evaluator. Does NOT run a generic checklist. Instead dispatches to: eval-ui-ux (screens/design), eval-code-quality (features/infrastructure), eval-integration (APIs/auth/payments), eval-business-logic (generator/rules/state). Triggered by: 'evaluate execution', 'review implementation', 'check build', '/phase-review'. Always runs after loop-executor.
    0
    installs
45. ▌
    Context Driven Development · ibrahim-3d

    Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
    0
    installs
46. ▌
    Dispatching Parallel Agents · ibrahim-3d

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
    0
    installs
47. ▌
    Knowledge Manager · ibrahim-3d

    Loads relevant patterns and known errors before track planning. Searches conductor/knowledge/ for solutions we've used before and errors we've encountered. Injects findings into the planner prompt to prevent reinventing solutions and repeating mistakes. Triggered automatically by orchestrator before PLAN step.
    0
    installs
48. ▌
    Subagent Driven Development · ibrahim-3d bundle

    Use when executing implementation plans with independent tasks in the current session
    0
    installs
49. ▌
    Retrospective Agent · ibrahim-3d

    Runs after every track completion to extract learnings. Analyzes what worked, what failed, and what patterns emerged. Updates conductor/knowledge/patterns.md with new solutions and errors.json with new error patterns. Proposes skill updates if workflow improvements are identified. Triggered automatically by orchestrator after COMPLETE step.
    0
    installs
50. ▌
    Finishing A Development Branch · ibrahim-3d

    Use 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 cleanup
    0
    installs
51. ▌
    Verification Before Completion · ibrahim-3d

    Use 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 always
    0
    installs