Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 60541–60570 of 65607 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| elegancesrid/smritiIteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| evidencesrid/smritiProduce visual PR evidence — a screenshot or a video — whenever a change has on-screen impact. If exercising the change would make the screen look different (a rendered view, an error/empty/loading/blocked state, a panel, layout, an icon, motion, a live update) a visual artifact is MANDATORY, not optional. A change can be backend by cause and visible by effect: tests are never a substitute for a visual artifact when there is on-screen impact. Capture rides the project's own Cucumber + Playwright e2e harness on an ephemeral pu box (video of a flow, or a still pulled from the clip), or drives a live kolu with the chrome-devtools MCP for a state no scenario reaches. Then transcode (ffmpeg), host on a GitHub release, and post a `## Evidence` comment. Triggers on "post evidence", "screenshot the change", "PR evidence", "record a video of this", "capture the UI", "show it working", "prove it", or finishing any change whose effect is visible on screen. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| fact-checksrid/smritiAudit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| forge-prsrid/smritiWrite engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| frontend-designsrid/smritiCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| hickeysrid/smritiEvaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| lens-debatesrid/smritiRun a structural-review debate between two lenses — lowy (volatility-based decomposition) and hickey (structural simplicity) — on the current diff. Each reviews independently, then they cross-examine every finding until they agree per-finding, and the agreed fixes are applied. Use when the user types `/lens-debate`, or asks to "have lowy and hickey review this", "run the lens debate", "debate this diff structurally", or "argue the structure of this PR until the lenses agree". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| lowysrid/smritiEvaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation). | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| nix-chrome-devtools-mcpsrid/smritichrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| nix-justfilesrid/smritiConventions for writing justfile recipes in Nix-based projects. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| nix-typescriptsrid/smritipnpm + Nix build conventions. Covers fetchPnpmDeps hash management and dependency workflow. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| pusrid/smritiProvision and drive a `pu` box — an Incus container used as a clean Linux host for CI, builds, and evidence capture. Use when you need to run something on a fresh remote box instead of the user's machine: `nix run` a build, run CI against a real host, capture screenshots/video off-machine, or reproduce on a pristine environment. Covers create/connect/scp/destroy, running remote commands, copying artifacts back, and the no-egress failure mode. Triggers on "pu box", "spin up a box", "run this on a box", "ephemeral host", "pu create/connect/destroy". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ralphsrid/smritiIterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| talksrid/smritiEnter talk mode — conversation and research, no repo changes. ONLY invoke when the user explicitly types `/talk` or `$talk`; never auto-select from a natural-language question or design discussion. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| build-orchestrationNagareNegishi/DJ-AppRun a multi-agent build session: the main session acts as manager — cutting a goal into units, spawning implementer, tester, and adviser subagents, and running the test-and-review loop to completion under anti-thrash guardrails. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| code-commentingNagareNegishi/DJ-AppApply whenever writing or editing code in any language, even if comments are not explicitly requested. Enforces comment and documentation discipline: concise file headers, function docs in the language's native format, inline comments for non-obvious logic, and protection of existing comments. Not required during suggestion-only or discussion when no file is written. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| comment-auditNagareNegishi/DJ-AppAudit the repository for comment coverage and bring under-commented source up to standard. Walks one file at a time, proposes comments per file for approval, and tracks progress to resume across sessions. Invoke with /comment-audit. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| dependency-upgradeNagareNegishi/DJ-AppUpgrade outdated dependencies one package at a time, with a changelog check for breaking changes and a test run between upgrades. Invoke with /dependency-upgrade; pass package names to limit scope. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| dev-researchNagareNegishi/DJ-AppUse this skill whenever the user needs help choosing between programming technologies, libraries, frameworks, tools, patterns, or architectural approaches. Covers all programming domains. Trigger even if the user doesn't say "suggest" explicitly — any programming decision where options exist and verification matters should use this skill. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| frontend-designNagareNegishi/DJ-AppImprove the visual design of the <project> frontend. Use when asked to improve, redesign, restyle, or enhance the UI in <frontend-dir>/. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| git-commitNagareNegishi/DJ-App | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| github-issue-creatorNagareNegishi/DJ-App | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| human-writingNagareNegishi/DJ-AppWrite documents in a plain, human voice and remove phrasing that reads as machine-generated. Use this skill EVERY time you produce a written artifact meant to be read by a person: READMEs, official documentation, design or planning docs, summaries, reports, proposals, release notes, changelogs, commit messages, GitHub issues, pull request descriptions, letters, emails, blog posts, and similar deliverables. Trigger it whenever the task is "write/draft/generate a doc" rather than answering a question in chat. Do NOT trigger it for direct conversational replies, inline explanations, or code. Run it in two passes: write the document, then re-read the finished draft and rewrite anything that signals a machine wrote it, presenting only the corrected version. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| issue-publishNagareNegishi/DJ-AppCreate or edit a GitHub issue with `gh` from the reviewed draft at `.github/drafts/issue-draft.md`. Use only when that draft exists and the user asks to publish, open, or file it — typically handed off from `github-issue-creator`. Assigns the issue to the user; never comments, closes, or reopens. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| label-setupNagareNegishi/DJ-AppCreate or reconcile a repository's labels from the preset in `labels.yml`. Writes labels only — never deletes, never touches labels outside the preset. Invoke with /label-setup. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| learning-mode-codingNagareNegishi/DJ-AppActivate when the user types "/learn" or "/learn <topic>". This switches Claude Code into a teaching-first coding mode for unfamiliar technologies. Do NOT trigger on any other signal — only the explicit /learn command. Once activated, stay in this mode for the remainder of the conversation unless the user says "/learn off". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| owasp-guardNagareNegishi/DJ-AppAutomatic OWASP Top 10:2025 compliance checker for all code suggestions and implementations. Use this skill whenever writing, reviewing, suggesting, or modifying code that touches security-relevant domains: authentication, authorization, database queries, user input handling, cryptography, HTTP endpoints, file I/O, error handling, dependency management, session management, configuration, logging, or API design. Also trigger when the user mentions OWASP, security review, secure coding, vulnerability check, or hardening. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| owasp-scanNagareNegishi/DJ-AppOn-demand OWASP Top 10:2025 security scanner. Scans a single file, captures cross-file connections for follow-up, and maintains a persistent findings record. Use when the user runs /owasp-scan with a file path, or asks to scan a file for security issues. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| owasp-updateNagareNegishi/DJ-AppUpdate the local OWASP cheat sheet cache. Use when the user explicitly runs /owasp-update to refresh cached OWASP Cheat Sheet Series content for the current project's language. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| plan-implNagareNegishi/DJ-AppUse this skill whenever the user wants a rough implementation plan — the "how", e.g. breaking a feature into build steps — from an existing product plan, or hands off from `plan-product`. Drafts a doc only; deep verification is the separate `plan-verify` skill. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |