All authors
Claude Skills by Najeebullah3124
github.com/Najeebullah3124264 skills0 installs6 views
- Ce Gemini ImagegenThis skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.Votes: 0GitHub stars: 2
- Ce IdeateGenerate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.Votes: 0GitHub stars: 2
- Ce OptimizeRun metric-driven iterative optimization loops. Define a measurable goal, build measurement scaffolding, then run parallel experiments that try many approaches, measure each against hard gates and/or LLM-as-judge quality scores, keep improvements, and converge toward the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation. Inspired by Karpathy's autoresearch, general...Votes: 0GitHub stars: 2
- Ce PlanCreate structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements...Votes: 0GitHub stars: 2
- Ce Polish Beta[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.Votes: 0GitHub stars: 2
- Ce Pr DescriptionWrite or regenerate a value-first pull-request description (title + body) for the current branch's commits or for a specified PR. Use when the user says 'write a PR description', 'refresh the PR description', 'regenerate the PR body', 'rewrite this PR', 'freshen the PR', 'update the PR description', 'draft a PR body for this diff', 'describe this PR properly', 'generate the PR title', or pastes a GitHub PR URL / #NN / number. Also used internally by ce-commit-push-pr (single-PR flow) and ce-p...Votes: 0GitHub stars: 2
- Ce ProofCreate, share, view, comment on, edit, and run human-in-the-loop review loops over markdown documents via Proof, the collaborative markdown editor at proofeditor.ai ("Proof editor"). Use when the user wants to render or view a local markdown file in Proof, share markdown to get a URL, iterate collaboratively on a Proof doc, comment on or suggest edits in Proof, HITL a spec/plan/draft for human review, sync a Proof doc back to local, or work from a proofeditor.ai URL. Trigger on phrases like "...Votes: 0GitHub stars: 2
- Ce Release NotesSummarize recent compound-engineering plugin releases, or answer a specific question about a past release with a version citation. Use when the user types `/ce-release-notes` or asks "what changed in compound-engineering recently?" or "what happened to `<skill-name>`?".Votes: 0GitHub stars: 2
- Ce Report BugReport a bug in the compound-engineering pluginVotes: 0GitHub stars: 2
- Ce Resolve Pr FeedbackResolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.Votes: 0GitHub stars: 2
- Ce Session ExtractExtract conversation skeleton or error signals from a single session file at a given path. Invoked by session-research agents after they have selected which sessions to deep-dive — not intended for direct user queries.Votes: 0GitHub stars: 2
- Ce Session InventoryDiscover session files for a repo across Claude Code, Codex, and Cursor, and extract session metadata (timestamps, branch, cwd, size, platform). Invoked by session-research agents — not intended for direct user queries.Votes: 0GitHub stars: 2
- Ce SessionsSearch and ask questions about your coding agent session history. Use when asking what you worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.Votes: 0GitHub stars: 2
- Ce SetupDiagnose and configure compound-engineering environment. Checks CLI dependencies, plugin version, and repo-local config. Offers guided installation for missing tools. Use when troubleshooting missing tools, verifying setup, or before onboarding.Votes: 0GitHub stars: 2
- Ce Slack ResearchSearch Slack for interpreted organizational context -- decisions, constraints, and discussion arcs that shape the current task. Produces a research digest with cross-cutting analysis and research-value assessment, not raw message lists. Use when searching Slack for context during planning, brainstorming, or any task where organizational knowledge matters. Trigger phrases: 'search slack for', 'what did we discuss about', 'slack context for', 'organizational context about', 'what does the team ...Votes: 0GitHub stars: 2
- Ce Test BrowserRun browser tests on pages affected by current PR or branchVotes: 0GitHub stars: 2
- Ce Test XcodeBuild and test iOS apps on simulator using XcodeBuildMCP. Use after making iOS code changes, before creating a PR, or when verifying app behavior and checking for crashes on simulator.Votes: 0GitHub stars: 2
- Ce UpdateCheck if the compound-engineering plugin is up to date and recommend the update command if not. Use when the user says "update compound engineering", "check compound engineering version", "ce update", "is compound engineering up to date", "update ce plugin", or reports issues that might stem from a stale compound-engineering plugin version. This skill only works in Claude Code — it relies on the plugin harness cache layout.Votes: 0GitHub stars: 2
- Ce Work Beta[BETA] Execute work with external delegate support. Same as ce-work but includes experimental Codex delegation mode for token-conserving code implementation.Votes: 0GitHub stars: 2
- Ce WorkExecute work efficiently while maintaining quality and finishing featuresVotes: 0GitHub stars: 2
- Ce WorktreeCreate an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.Votes: 0GitHub stars: 2
- LfgFull autonomous engineering workflowVotes: 0GitHub stars: 2
- Customaize AgentGuide for creating effective skills using a TDD-based approach. This command treats skill creation as Test-Driven Development applied to process documentation. - Purpose - Create reusable skills that extend Claude's capabilities - Output - Complete skill directory with SKILL.md and optional resources ```bash /customaize-agent:create-skill ["skill name"] ```Votes: 0GitHub stars: 2
- Customaize AgentVerify skills work under pressure and resist rationalization using the RED-GREEN-REFACTOR cycle. Critical for discipline-enforcing skills. - Purpose - Test skill effectiveness with pressure scenarios - Output - Verification report with rationalization table ```bash /customaize-agent:test-skill ["skill path or name"] ```Votes: 0GitHub stars: 2
- Create CommandInteractive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integrationVotes: 0GitHub stars: 2
- Test PromptUse when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testingVotes: 0GitHub stars: 2
- Review Local ChangesComprehensive review of local uncommitted changes using specialized agents with code improvement suggestionsVotes: 0GitHub stars: 2
- Review PrComprehensive pull request review using specialized agentsVotes: 0GitHub stars: 2
- Do And JudgeExecute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loopVotes: 0GitHub stars: 2
- Do CompetitivelyExecute tasks through competitive multi-agent generation, meta-judge evaluation specification, multi-judge evaluation, and evidence-based synthesisVotes: 0GitHub stars: 2
- Do In ParallelLaunch multiple sub-agents in parallel to execute tasks across files or targets with intelligent model selection, quality-focused prompting, and meta-judge → LLM-as-a-judge verificationVotes: 0GitHub stars: 2
- Do In StepsExecute complex tasks through sequential sub-agent orchestration with intelligent model selection, meta-judge → LLM-as-a-judge verificationVotes: 0GitHub stars: 2
- Launch Sub AgentLaunch an intelligent sub-agent with automatic model selection based on task complexity, specialized agent matching, Zero-shot CoT reasoning, and mandatory self-critique verificationVotes: 0GitHub stars: 2
- Add Taskcreates draft task file in .specs/tasks/draft/ with original user intentVotes: 0GitHub stars: 2
- BrainstormUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processesVotes: 0GitHub stars: 2
- Implement TaskImplement a task with automated LLM-as-Judge verification for critical stepsVotes: 0GitHub stars: 2
- Plan TaskRefine, parallelize, and verify a draft task specification into a fully planned implementation-ready taskVotes: 0GitHub stars: 2
- Write TestsSystematically add test coverage for all local code changes using specialized review and development agents. Add tests for uncommitted changes (including untracked files), or if everything is commited, then will cover latest commit.Votes: 0GitHub stars: 2
- Docs StyleStyle guidelines for writing and updating documentation. Use when writing new docs, updating existing docs, or reviewing docs for quality.Votes: 0GitHub stars: 2
- Cn CheckInstall and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.Votes: 0GitHub stars: 2
- Cache ExpertCovers Dagger Engine caching internals including cache key derivation, invalidation, and the immutable DAG model. Use when debugging cache misses, unexpected invalidations, or implementing caching-related engine features.Votes: 0GitHub stars: 2
- Dagger ChoresHandle quick, repeatable Dagger repository maintenance chores. Use when the user asks for small operational changes and wants the same established edits and commit style applied quickly.Votes: 0GitHub stars: 2
- Dagger CodegenEdit dagger.gen.go output, Go templates (object.go.tmpl, defs.go.tmpl), invoke() dispatch, SDK interfaces (CodeGenerator, ClientGenerator), `dagger develop`, `dagger client install`. Keywords: codegen, SDK, bindings, templates, internal/dagger, dag.*, ModuleMainSrcVotes: 0GitHub stars: 2
- Dagger Design ProposalsWrite design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.Votes: 0GitHub stars: 2
- Engine Dev TestingHow to test Dagger engine changes. Covers manual e2e testing via the playground (bootstrapping a dev engine from source, running commands inside it, capturing crash logs) and running the integration test suite. Use when modifying engine code (engine/server, core/, dagql/) and needing to verify changes work. Triggers on: testing engine changes, dev engine, playground, e2e test, engine crash, debug engine, manual testing, verify engine fix.Votes: 0GitHub stars: 2
- Component RefactoringRefactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.Votes: 0GitHub stars: 2
- E2e Cucumber PlaywrightWrite, update, or review Dify end-to-end tests under `e2e/` that use Cucumber, Gherkin, and Playwright. Use when the task involves `.feature` files, `features/step-definitions/`, `features/support/`, `DifyWorld`, scenario tags, locator/assertion choices, or E2E testing best practices for this repository.Votes: 0GitHub stars: 2
- Frontend Query MutationGuide for implementing Dify frontend query and mutation patterns with TanStack Query and oRPC. Trigger when creating or updating contracts in web/contract, wiring router composition, consuming consoleQuery or marketplaceQuery in components or services, deciding whether to call queryOptions() directly or extract a helper or use-* hook, handling conditional queries, cache invalidation, mutation error handling, or migrating legacy service calls to contract-first query and mutation helpers.Votes: 0GitHub stars: 2
- Frontend TestingGenerate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.Votes: 0GitHub stars: 2
- Claude ApiAnthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.Votes: 0GitHub stars: 2