Explore skills
Showing 64111–64140 of 77079 skills
TsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexTsukiNi22/ai-utils
Stars: 1Claude CodeCodexCreate beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
Biswadipgoj/biswodip
Stars: 1Claude CodeCodexDesign, build, validate, and ship cross-platform agent skills. Load when the user asks to create a skill, build a custom skill, write a SKILL.md, package a workflow as reusable agent capability, improve or audit a skill, publish a skill, or build a planned skill suite.
dvy1987/agent-loom
Stars: 4Claude CodeCodexAutomates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
ecoDriverltd/FoundryAgentsExperiment
Stars: 0Claude CodeCodexPM skill for Claude Code, Codex, Cursor, and Windsurf. Diagnoses SaaS metrics, critiques PRDs, plans roadmaps, runs discovery, coaches PM career transitions, pressure-tests AI product decisions, and designs PLG growth strategies. Seven knowledge domains, 12 templates, 40+ frameworks, and an opinionated interaction style that labels assumptions and names tradeoffs.
Digidai/product-manager-skills
Stars: 205Claude CodeCodexQuickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexThe arcade's type system: the Fraunces and Outfit pairing, the roles each face plays, the numeric styling that game UI lives on, and the sizing floor set by measured contrast headroom. Use when adding or restyling any text, number, label or button in Payload, Ledger Lane or the hub, when choosing a size or weight, or when text feels cramped, illegible or off-brand.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexDesign principles for this repo's genre: daily puzzles, engine-builder runs, and the rules that make compounding scores feel earned rather than arbitrary. Use when adding a part, tuning a quota curve, designing a boss twist, changing what a draft offers, or judging whether a proposed mechanic is fun.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexOrchestrate a feature or fix from story to PR through the team's AI-SDLC workflow, with human checkpoints: story -> plan -> branch -> TDD (>=80% coverage, story-tagged tests) -> update both doc layers -> record decisions as ADRs -> enrich the work item -> review -> PR. Use when the user says "take this story through the process", "run the dev cycle", "do the full workflow on MN-42", or "build this end to end properly". It delegates to focused skills rather than doing each step itself. Do NOT use for a quick one-off edit, a question, or a standalone git or branch request (creating or naming a branch on its own) - use the individual skills directly for those.
tsunami28/MindNova
Stars: 0Claude CodeCodexImprove the internal structure of existing code without changing its observable behaviour. Use when the user says "refactor this", "clean this up", "simplify this", "extract a method/class", "rename for clarity", "reduce this duplication", or "tidy this without changing behaviour". The defining constraint is behaviour preservation: the tests pass before and after, and the public contract is unchanged. Do NOT use to add or change behaviour, fix a bug, or build a feature (that is create-code-generation), and do NOT use to delete dead code as the primary goal.
tsunami28/MindNova
Stars: 0Claude CodeCodexAssemble refined, sized stories into an iteration and order them by dependency and value so the build phase starts with a clear, unblocked queue. Use when the user says "plan the sprint", "what should we pick up next", "fill the iteration", "sequence these stories", "order the backlog for the next sprint", or "assign these to the sprint". This is a light coordination step, not a document-producing one. Do NOT use to create or refine a story (that is elaboration-upsert-user-story), to write acceptance criteria (that is elaboration-upsert-user-story-acceptance-criteria), to take a single story through build (that is create-code-generation), or to report the next step on a single work item (that is run-sdlc).
tsunami28/MindNova
Stars: 0Claude CodeCodexMaintain BOTH documentation layers as one linked wiki after a change: technical docs in docs/ and functional docs in docs-functional/. Use after implementing or changing a feature, when the user says "update the docs", "sync the documentation", "the docs are out of date", "document how this works", or as the documentation step of a development cycle. Also use when a good answer to a real question deserves to become a page. Reads the layer index first, routes each change to the right layer, cross-links related pages, and flags stale sections. Do NOT use for ADRs (governance-author-adr), the constitution (governance-constitution), or API spec / OpenAPI generation.
tsunami28/MindNova
Stars: 0Claude CodeCodexVerify a change is adequately tested before it ships: run the tests, measure line coverage on the changed projects, and confirm every acceptance criterion has a covering test. Use when the user says "is this tested enough", "check the coverage for MN-42", "are all the ACs covered", "verify the tests before the PR", "run the QE checks", or "is this story gate-ready". Do NOT use to WRITE the implementation or the tests (that is create-code-generation), to derive or number the criteria (that is elaboration-upsert-user-story-acceptance-criteria), or to review code style (that is the review step).
tsunami28/MindNova
Stars: 0Claude CodeCodexProduce a machine-readable API specification (OpenAPI 3.x in YAML) for the slice being built, so the build and tests consume a contract instead of prose. Use when designing or changing a REST endpoint, when the user says "design the API for this", "write the OpenAPI spec", "define the contract for MN-42", "what should the request/response shape be", or before code generation begins on a slice that exposes or changes an HTTP surface. This is the L3 keystone: the contract lives in the repo. Do NOT use to author an ADR (that is governance-author-adr), to write feature docs, to generate the implementation (that is create-code-generation), or for non-HTTP work.
tsunami28/MindNova
Stars: 0Claude CodeCodexSuggest and author Architecture Decision Records (MADR-style) in docs/adrs/. Use when a load-bearing decision is being made or has just been made ("we decided to...", "let's go with X over Y", "should this be an ADR?", "record this decision", "write an ADR", "supersede ADR NNNN"), or when reviewing a plan/change that implies an unrecorded architectural choice. Also use to detect and flag decisions that ought to be recorded. Do NOT use for the project-wide constitution (that is the governance-constitution skill), for ordinary feature docs, or for tracker tickets.
tsunami28/MindNova
Stars: 0Claude CodeCodexUpdate an existing local work item (under docs/discovery/) so its content reflects current reality after work ships or scope changes: splice shipped behavior, decisions, and approach into the matching section, fix a stale title, add related-item links with the reason for each, and backlink ADRs, designs, and docs. Use when the user says "add this to MN-42", "enrich MN-42", "the ticket should say what we actually shipped", "update the description to match reality", "link these items and say why", "record this decision on the story", or finishes work that changed what the story is or produced an artifact worth recording. Invoking it is a directive to WRITE the file after one confirmation, not to leave a proposal. Do NOT use to CREATE a work item (that is elaboration-upsert-user-story) or to read or search items.
tsunami28/MindNova
Stars: 0Claude CodeCodexTriage an incoming work item (under docs/discovery/) - a bug report, request, or incident - so it is correctly understood, classified, and routed before anyone builds. Use when the user says "triage MN-42", "is this a real bug?", "can you reproduce this?", "what priority is this", "is this a duplicate", "look into this report/incident", or hands you an inbound item to assess. Reads the item and its evidence, reproduces or characterises the problem, classifies and prioritises it, checks for duplicates, and records a triage note. Do NOT use to CREATE an item (that is elaboration-upsert-user-story), to rewrite an item's content (that is governance-enrich-ticket), or to implement the fix (that is mature-resolve-ticket).
tsunami28/MindNova
Stars: 0Claude CodeCodexResolve a confirmed defect surfaced in the mature phase by running a scoped pass of the development cycle. Use when a triaged work item is a reproducible bug ready to fix: phrasings like "fix MN-42", "this defect is confirmed, go fix it", "resolve the bug from triage", "take this confirmed defect through the dev cycle", or when mature-analyze-ticket has handed off a confirmed reproduction. This is a thin entry point that frames the defect and delegates. Do NOT use to triage or confirm an issue first (that is mature-analyze-ticket), to build a new feature or make an ad-hoc code fix with no triaged ticket (use create-code-generation directly), or for a pure structural cleanup with no behaviour change (that is create-refactoring).
tsunami28/MindNova
Stars: 0Claude CodeCodexUse for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
hgxszhj/https-github.com-zhaoxuya520-reverse-skill
Stars: 1Claude CodeCodexUse for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.
hgxszhj/https-github.com-zhaoxuya520-reverse-skill
Stars: 1Claude CodeCodexUse when analyzing suspected malware through static, dynamic, and behavioral techniques, including IOC extraction, YARA or Sigma rules, sandboxing, and anti-analysis behavior.
hgxszhj/https-github.com-zhaoxuya520-reverse-skill
Stars: 1Claude CodeCodexUse for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks.
hgxszhj/https-github.com-zhaoxuya520-reverse-skill
Stars: 1Claude CodeCodexPromote Doppel world builds across social platforms. Use when the agent wants to share builds on Twitter/X, Farcaster, Telegram, or Moltbook to drive observers, grow reputation, and recruit collaborators.
kbarbel640-del/skills
Stars: 1Claude CodeCodexDesign, preview, and generate UI code using Google Stitch (via MCP). Helps developers choose the best UI by generating previews first, allowing iteration, and then exporting code.
kbarbel640-del/skills
Stars: 1Claude CodeCodex