Explore skills
Showing 20611–20640 of 71536 skills
Audits documentation and comments for trust, coverage, consistency and freshness; read-only.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexAudits cross-cutting codebase health, security and maintainability; not a single-change review or specialist audit.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexAudits existing tests for risk coverage, reliable oracles and maintenance value; does not edit tests.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexAudits implemented architecture boundaries, dependencies, ownership and state lifecycles; not target design or plan review.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexAudits queries, transactions, consistency and persistence resource lifetimes; read-only.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexReviews skill instructions, trigger boundaries and distribution contracts; not product code.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexCreates and maintains Figma Code Connect files (`*.figma.tsx`) that map Figma components to code via the parser-based `figma.connect()` API. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.tsx files.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when creating, naming, or placing a file or folder in libs/*, or when modifying or adding a file to an existing component (even when the barrel isn't touched) — component vs utility naming, the one-responsibility-per-file layout, when a folder needs an `index.ts` barrel (public API only), and the required set of files a component needs per lib. Load this before scaffolding or restructuring a component so the layout matches the codebase.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when designing or changing a component's public API, its composition, or its state model in libs/ui-react or libs/ui-rnative — layering (core vs internal vs primitives), BaseProps/Props splits, converting a component to compound / changing its composition with createSafeContext, controlled/uncontrolled state, prop-naming conventions, and cross-platform API parity. Load this before shaping a new component, changing its props, or refactoring its composition.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, controls, and export naming conventions.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when writing or editing component tests in libs/ui-react or libs/ui-rnative — shared structure and coverage conventions, plus the per-platform runner: Vitest + React Testing Library on web, Jest + React Native Testing Library on RN. Load this before writing tests.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when asked to test a Lumen change against consumer repos before releasing it: a breaking or architectural change, a lint-plugin upgrade, peer/prod dependency moves, build or packaging changes, or to check how consumers use a component, prop or variant. Runs the change (or a usage scan) across the production consumers in the adoption registry and outputs a shareable HTML report.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when asked how other design systems handle a component, prop, token or pattern; to name a component, prop or token; to research best practices (composition, when to split, a11y, responsiveness, motion) before building; or for a design-system discovery or benchmark report. Compares Coinbase CDS, Adobe Spectrum, Astryx, Material, Primer, MetaMask DS and Base UI, anchors the recommendation in Lumen's code, and outputs a shareable HTML report.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when implementing or updating a component from a Figma link — how to turn the Figma design variables into code tokens, on both platforms: Tailwind classnames for libs/ui-react and themeJS (`t.*`) paths for libs/ui-rnative. For the full token catalogues and styling mechanics, see component-styling.
LedgerHQ/lumen
Stars: 25Claude CodeCodexSync processed CSS design tokens with JavaScript theme objects for React Native. Use when aligning tokens after Figma sync, checking token consistency, or updating JS theme files manually.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when asked to check Lumen version adoption across consumer repos, generate the Lumen adoption report, or find which repos are behind on a Lumen package version, or who owns those repos.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUpgrade a consumer repo to the latest Lumen: audit the gap, bump every `@ledgerhq/lumen-*` package, apply each migration crossed, verify, and open the PR. Run from the consumer repo's root, only when asked to upgrade or audit Lumen there.
LedgerHQ/lumen
Stars: 25Claude CodeCodexOpen a PR from the current branch to `main`: find the DLS ticket in the current sprint, ensure an Nx version plan exists, commit, push, and create the PR from the repo's PR template. Run only when the user explicitly asks to open/create a PR.
LedgerHQ/lumen
Stars: 25Claude CodeCodexReview a PR or the current branch for a Lumen design-system change — routes each changed file to React (web/Tailwind) or React Native (useStyleSheet) guidelines, checks the Nx version plan, and reports a flat, severity-scored finding list. Use when the user asks to review a PR, review code changes, check a branch, do a local code review, or provides a GitHub PR URL.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse when generating or editing an Nx version plan in .nx/version-plans/ — the bump type must always be `patch`, one package per file, and the message one `type(Scope): summary` line.
LedgerHQ/lumen
Stars: 25Claude CodeCodexWrites the migration file (in `libs/migrations/src/`) and the Nx version plans for the current branch's changes to Lumen's public API. Use when a branch removes, renames or changes an export, prop, prop value, token, icon or peer dependency, changes behavior or rendering consumers rely on, when `check:breaking-changes` or the migrations `validate` fails, or when asked to write a migration or prepare a breaking change for review.
LedgerHQ/lumen
Stars: 25Claude CodeCodexUse on the first conversation after someone imports the emerging-keyword monitor template: onboard them one question at a time.
Pluviobyte/saas-growth-agents
Stars: 541Claude CodeCodexUse when setting up or running daily emerging-keyword / meme monitoring: sources, gates, prescan→broadcast schedule, Trends cost controls, and report format.
Pluviobyte/saas-growth-agents
Stars: 541Claude CodeCodexnexu-io/open-design
Stars: 108kClaude CodeCodexnexu-io/open-design
Stars: 108kClaude CodeCodexnexu-io/open-design
Stars: 108kClaude CodeCodexnexu-io/open-design
Stars: 108kClaude CodeCodexFinds loops where the user keeps acting as a manual step for agents (retrying, judging output, approving, carrying context, starting the same task by hand, doing the agent's work) and proposes how to lift the user out: delete a stale rule, change a skill / AGENTS.md / playbook, add a script or metric, add a skill or scheduled task, or advise the user. Keeps a private loop ledger and promotes Claude Code auto-memory into artifacts. With a task already in the session, reflects on that session; in an empty session, scans recent local Claude Code, MiniMax Code, omp, pi and Codex sessions, a claude.ai export and an Obsidian vault. Triggers: /lifting-loops, retro, post-task reflection, "find repeated work", 反思一下, 复盘这次会话, 总结最近的会话, 找找重复劳动, 哪些事可以不用我; the weekly scheduled run; settling a proposal ("accept P-003", 采纳 P-003, 拒绝 P-003).
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexWrite multiple-choice questions that check whether a PR's author understands their change. Use only when the MCode Review pipeline asks for an author quiz.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex