Showing 33871–33900 of 77205 skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
irinabuht12-oss/marketing-skills
Review code for quality, simplicity, and common mistakes before declaring work complete.
srid/drishti
Iteratively 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.
srid/drishti
Audit 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.
srid/drishti
Evaluate 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.
srid/drishti
Evaluate 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).
srid/drishti
odu MCP server launcher — drive CI from a coding agent. `bin/serve` resolves odu via Nix and runs `odu mcp` in the cwd. See the repo README for the tools/resources and override knobs.
srid/drishti
Iterative 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.
srid/drishti
Enter 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.
srid/drishti
Builds and designs React Native Nitro Modules with Nitrogen, HybridObject TypeScript specs, Nitro View components, generated native implementations, zero-copy and native-state APIs, Swift/Kotlin/C++ bindings, example apps, and testing. Use when creating a Nitro Module, adding or reviewing HybridObjects, building a Nitro View (HybridView) component, designing Nitro-specific public APIs, implementing native functionality, or setting up the nitrogen codegen pipeline. Pair with api-design for general library API shape.
jonluca/palate