Explore skills
Showing 56521–56550 of 71509 skills
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Souvik-223/agent-skills-agentic-tools
Stars: 0Claude CodeCodexDocumentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
Souvik-223/agent-skills-agentic-tools
Stars: 0Claude CodeCodexMain application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Souvik-223/agent-skills-agentic-tools
Stars: 0Claude CodeCodexDocumentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
Souvik-223/agent-skills-agentic-tools
Stars: 0Claude CodeCodexAudits and remediates web accessibility against WCAG 2.2 Level AA. Checks keyboard reachability, tab order, focus management, visible focus, screen-reader semantics (HTML, ARIA, name/role/value), color contrast, hit-target size, reduced motion, form labels and errors, live regions, heading and landmark structure, and image/media alternatives. Produces tiered findings — Blocker / High / Medium with success-criterion citations, plus a separate Polish tier for best-practice items below AA. Also writes accessibility specs for new components (keyboard model, ARIA pattern, focus order, error semantics) and explains why a pattern fails. Triggers on "accessibility", "a11y", "wcag", "keyboard navigation", "tab order", "skip link", "screen reader", "aria", "semantic html", "alt text", "color contrast", "focus ring", "focus order", "focus trap", "reduced motion", "hit target", "touch target", "live region", "landmark", "heading order", "a11y audit", "accessibility audit", "axe", "section 508".
apuya/react-basics-ui
Stars: 0Claude CodeCodexDesigns and maintains build tooling — bundlers (Vite, Webpack, Rollup, esbuild, Parcel, tsup), package managers (npm, pnpm, yarn, Pipenv, Poetry, uv), lockfile hygiene, pre-commit hooks, runtime pinning, build cache, module resolution, monorepo workspaces, reproducibility. Audits for non-deterministic builds, lockfile drift, mixed package managers, unpinned runtimes, broken caches, and hooks that mutate without staging. Use when adding a bundler, switching package managers, debugging slow or non-reproducible builds, configuring pre-commit, or laying out a monorepo. Triggers on "build", "bundler", "vite", "webpack", "rollup", "esbuild", "parcel", "tsup", "swc", "babel", "npm", "pnpm", "yarn", "pipenv", "poetry", "uv", "pip-tools", "lockfile", "pre-commit", "husky", "lefthook", "build cache", "slow build", "hmr", "tree shaking", "code splitting", "monorepo", "workspace", "turborepo", "nx", "reproducible build", ".nvmrc", ".python-version", "engines field", "build toolchain".
apuya/react-basics-ui
Stars: 0Claude CodeCodexHelps with git commits and preparing changes. Use when user wants to commit, asks what changed, or wants to see git status. Triggers on "commit", "git", "push", "what changed", "stage", "diff".
apuya/react-basics-ui
Stars: 0Claude CodeCodexBuilds and audits reusable presentational UI components in Storybook — props in, events out, no fetching, routing, global state, or domain types. Designs minimal prop APIs (controlled/uncontrolled, ref forwarding, native prop passthrough), enumerates visual variants and interaction states, writes stories per variant and per state plus interaction stories with play functions, and audits components for business-logic leaks, API smells, and missing story coverage. Use when authoring a presentational component, organizing Storybook stories, refactoring a prop API, extracting logic out of a UI primitive, or auditing a component library. Triggers on "storybook", "story", "presentational component", "dumb component", "ui component", "reusable component", "component api", "component props", "component variants", "component states", "controlled component", "extract logic", "business logic in component", "ref forwarding", "play function", "interaction story", "component audit".
apuya/react-basics-ui
Stars: 0Claude CodeCodexGuards react-basics-ui's design token system (primitive → semantic, with a legacy component tier) and the UI primitive component layer. Enforces no raw hex/rgb/px in components, components consuming semantic tokens only, dark-theme parity under [data-theme="dark"], and no dangling var() references. Use when adding or changing design tokens, building or reviewing primitive components, or auditing a codebase for hardcoded visual values. Triggers on "design token", "new token", "semantic token", "primitive component", "raw hex", "hardcoded color", "dark mode parity", "token audit", "css variable", "design system".
apuya/react-basics-ui
Stars: 0Claude CodeCodexRuns linting, formatting, and type checks for react-basics-ui. Triggers on "lint", "pre-commit", "format", "eslint", "prettier", "tsc", "type check", "code quality".
apuya/react-basics-ui
Stars: 0Claude CodeCodexDesigns, configures, audits Storybook 8+ workspaces in Component Story Format 3 (CSF3). Writes meta/StoryObj-typed stories — args, argTypes, parameters, decorators, loaders — and play functions with `@storybook/test`. Covers default, variant-matrix, per-state, and interaction stories. Configures `.storybook/main.ts`, `.storybook/preview.tsx`, addons (a11y, controls, docs, interactions, themes, viewport, msw, vitest, chromatic), autodocs/MDX, theming decorators, and MSW network mocking. Sets up the test runner, the Vitest addon, and Chromatic visual regression. Audits for missing variants/states, real network calls, brittle mocks, assertion-free play functions, and stories duplicating snapshots. Triggers on "storybook", "csf3", ".stories.tsx", "storyobj", "argtypes", "play function", "interaction test", "storybook addon", ".storybook/main", ".storybook/preview", "autodocs", "mdx", "storybook test runner", "storybook vitest", "msw storybook", "chromatic", "visual regression", "story composition".
apuya/react-basics-ui
Stars: 0Claude CodeCodexWrites and audits Tailwind CSS v4 in react-basics-ui — the CSS-first setup (@import "tailwindcss", @theme), the arbitrary-value-referencing-CSS-variable convention (bg-[color:var(--semantic-*)]), the cn() helper (clsx + tailwind-merge), and the co-located .styles.ts class-map pattern. Knows the v4 gotcha that tailwind.config.js is only loaded via @config and that named utilities are dead without it. Use when adding or changing Tailwind classes, building a component's styles, choosing between named utilities and arbitrary values, wiring design tokens into utilities, or auditing className usage. Triggers on "tailwind", "tailwindcss", "utility class", "className", "arbitrary value", "var(--semantic", "cn(", "clsx", "tailwind-merge", "twMerge", ".styles.ts", "@theme", "@config", "@apply", "tailwind.config", "responsive variant", "breakpoint", "dark mode tailwind", "hover:", "focus-visible:", "dead utility".
apuya/react-basics-ui
Stars: 0Claude CodeCodexRuns tests and helps write test cases for react-basics-ui. Use when user asks to run tests, write tests, check if tests pass, or mentions testing. Triggers on "test", "run tests", "write tests", "vitest", "coverage".
apuya/react-basics-ui
Stars: 0Claude CodeCodexEncodes invariants in the type system so illegal states cannot be constructed. Picks between newtypes, smart constructors, discriminated unions, and phantom types based on the invariant being protected. Audits code for primitive obsession, boolean blindness, stringly-typed data, partial functions, and validation that should be parsing. Decides what belongs in types (structure, identity, state, ordering) versus tests (behaviour, IO, time). Triggers on "type-driven development", "type first", "make illegal states unrepresentable", "illegal state", "parse don't validate", "smart constructor", "branded type", "newtype", "phantom type", "discriminated union", "sum type", "algebraic data type", "adt", "exhaustiveness", "never type", "refinement type", "primitive obsession", "boolean blindness", "stringly typed", "partial function", "encode invariant", "types as tests", "type safety", "as const", "satisfies".
apuya/react-basics-ui
Stars: 0Claude CodeCodexOwns the visual layer of a UI — color palette and semantic application, typography (type scale, weight, tracking, line height, font selection), spacing rhythm and density, illustration, iconography, and pixel-accurate Figma mockups. Audits visual hierarchy, color contrast against semantic intent, dark-mode parity, and visual states (default, hover, pressed, focus, disabled). Decides what the UI looks like once UX structure is settled. Does not own user flows, wireframes, interaction patterns, design-token taxonomy, or WCAG audits — those are separate concerns. Triggers on "ui designer", "ui design", "visual design", "visual hierarchy", "visual treatment", "visual review", "visual audit", "typography", "type scale", "font selection", "color palette", "color contrast", "dark mode", "spacing system", "illustration", "iconography", "mockup", "pixel-perfect", "high-fidelity mockup", "figma mockup", "visual polish".
apuya/react-basics-ui
Stars: 0Claude CodeCodexManages branch naming, version tracking, and branch lifecycle. Use when user wants to create, list, rename, or clean up branches, or asks about versioning. Triggers on "branch", "version", "new branch", "create branch", "rename branch", "cleanup branches", "what version", "release".
apuya/react-basics-ui
Stars: 0Claude CodeCodexKochab, a personalized resume-based job-search assistant that runs a recurring scan and everything downstream of it. Use when the user wants to start or run a job search, shares a resume, or says "set up my job scan," "find roles that fit my resume," or "what should I apply to." Also use to tailor a resume, draft a cover note or application email, build a story bank, make a study plan for a gap ("what should I study," "how do I qualify for [role]"), prep for an interview, track the pipeline ("I applied to," "where does my search stand"), keep the search moving ("should I follow up," "I'm not interested in [role]"), get stage guidance or references, handle offers and negotiation ("I got an offer"), recover from a rejection or withdraw cleanly, adjust the coaching dial, or use the network ("do I know anyone at [employer]"). It drafts materials and tracks the whole search from discovery to offer; the user always sends.
btmoriarty/kochab
Stars: 2Claude CodeCodexResearch a company and a specific role, then produce an honest brief on whether it is worth pursuing. Use this whenever the user mentions a recruiter reaching out, a job posting they found, a company someone told them about, or a role they are weighing. Triggers on "a recruiter contacted me," "should I apply to," "what do you know about [company]," "look into this company," "is this role real," "assess this posting," "vet this opportunity," "a friend mentioned a job at," or when the user pastes a job description, recruiter email, or LinkedIn InMail. Also triggers on "compare these two roles" and "what should I ask the recruiter."
btmoriarty/kochab
Stars: 2Claude CodeCodexRun a short product-discovery interview with a user of Kochab to surface what they actually need, then turn it into structured roadmap input. Use when someone says "interview me about features," "run the roadmap interview," "I have feedback on the tool," "what should this tool do next," or when a maintainer wants to gather feature ideas from a user. Produces per-user notes plus an append to a shared feature backlog, so requests that recur across users rise to the top.
btmoriarty/kochab
Stars: 2Claude CodeCodexAudit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexTranslate or update localized Markdown and MDX content in Astro projects while preserving content identity, executable examples, components, assets, and locale navigation. Use when a source article and target locale are provided or inferable from the request.
rgglez/rgglez-dev-skills
Stars: 0Claude CodeCodexTranslate or update localized Markdown and MDX content in Astro projects while preserving content identity, executable examples, components, assets, and locale navigation. Use when a source article and target locale are provided or inferable from the request.
rgglez/rgglez-dev-skills
Stars: 0Claude CodeCodexUse when a parallel artifact integration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the integration staging plan containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a parallel artifact integration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the integration staging plan with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the parallel artifact integration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the integration staging plan with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the parallel artifact integration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the integration staging plan with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the parallel artifact integration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the integration staging plan with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the parallel artifact integration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the integration staging plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a decision about parallel artifact integration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the integration staging plan. Success means each material claim has a source, version/date, location, and confidence note; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a delegated task cancellation propagation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cancellation propagation check containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodex