All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 62,560
- 2,607
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse development skills
Showing 9,769–9,792 of 62,560 skills
- Java Clean CodeComplete Clean Code reference for Java 21+ in one skill — naming, methods, comments, general quality, and tests, with modern idioms (records, sealed types, pattern matching, Optional, streams). Use when writing, reviewing, or refactoring any Java code and you want the whole catalog at once rather than one focused area.Votes: 0GitHub stars: 2
- Java Boy ScoutApplies the Boy Scout Rule to Java — leave every file a little cleaner than you found it, with small safe improvements made alongside the change you were asked for. Use when fixing, editing, debugging, or extending existing Java code, and when the user says "while you're at it", "any quick wins", "tidy this up", "improve this a bit", or you are already editing a file that has obvious small problems nearby.Votes: 0GitHub stars: 2
- Go TestsEnforces idiomatic Go testing — table-driven cases with subtests, the standard library over assertion frameworks, t.Cleanup for teardown, httptest for HTTP, golden files, fuzzing, and benchmarks that measure. Use when writing or reviewing Go tests, and when the user mentions table tests, t.Run, t.Parallel, testify, testdata, golden files, httptest, go test -race, coverage, benchmarks, fuzz, or asks "how do I test this in Go".Votes: 0GitHub stars: 2
- Go InterfacesEnforces Go interface design — interfaces defined by the consumer, kept to one or two methods, accepted as parameters while structs are returned, and never created before a second implementation exists. Use when writing or reviewing Go abstractions, mocks, or package boundaries, and when the user mentions interface design, mocking, dependency injection, "accept interfaces return structs", io.Reader, io.Writer, generics vs interfaces, or asks "should this be an interface", "how do I test this ...Votes: 0GitHub stars: 2
- Go IdiomEnforces idiomatic Go style — name length scaled to scope, no stutter, useful zero values, guard clauses, correct defer placement, composition over inheritance, and doc comments in the required form. Use when writing, reviewing, or refactoring any Go code, and when the user asks whether something is idiomatic, mentions gofmt, go vet, golangci-lint, package naming, receiver names, struct embedding, or asks "is this Go-ish", "does this read like Go", "clean up this Go".Votes: 0GitHub stars: 2
- Go ErrorsEnforces Go error handling — errors as values, wrapping with %w, errors.Is and errors.As over type assertions, sentinel and custom error types, and when panic is acceptable. Use when writing, reviewing, or debugging Go error paths, and when the user mentions err != nil, error wrapping, errors.Is, errors.As, sentinel errors, panic, recover, errors.Join, or asks "how should I return this error", "why is errors.Is failing", "should this panic".Votes: 0GitHub stars: 2
- Go ConcurrencyEnforces safe Go concurrency — every goroutine has a known stop condition, context propagates cancellation, channel ownership and direction are explicit, and shared state is protected or not shared. Use when writing or reviewing Go that starts goroutines, uses channels, sync primitives, or context, and when the user mentions goroutine leaks, deadlock, data race, WaitGroup, errgroup, select, mutex, worker pool, "-race", or asks "is this concurrent code safe", "why does this hang".Votes: 0GitHub stars: 2
- Go Api DesignEnforces Go package and API design — small exported surfaces, packages named for what they provide, functional options instead of growing constructors, context first, no init side effects, and changes that stay backward compatible. Use when creating or restructuring Go packages, designing an exported API or library, or reviewing a public interface, and when the user mentions package layout, internal/, functional options, breaking changes, semantic import versioning, or asks "how should I stru...Votes: 0GitHub stars: 2
- Design PatternsSelects, applies, and pushes back on the 23 Gang of Four design patterns. Covers intent, fit, trade-offs, and the cheaper alternative that usually wins. Use when choosing between patterns, naming an existing structure, or refactoring toward one — and when the user says "which pattern", "what pattern should I use", "design pattern", "GoF", "factory", "strategy", "observer", "decorator", "adapter", "singleton", "visitor", or describes a shape a pattern solves: swappable algorithms, notifying su...Votes: 0GitHub stars: 2
- Unit Test WriterPlans and implements comprehensive unit tests for the PABX monorepo — Angular frontend (Jest + jest-preset-angular, .spec.ts) and Node.js backend (Jest, apps/backend/__tests__/unit/). Runs interactively (3 phases with an approval checkpoint) when called by a user, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing test flagged by the evaluator. Enforces PABX rules (real component imports, manual service instantiati...Votes: 0GitHub stars: 3
- Unit Test ValidatorAudits unit tests in the PABX monorepo (Angular frontend .spec.ts + Node.js backend __tests__/unit/) against the unit-test-writer rules, producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected test conforms before resuming evaluation, or run directly by a user.Votes: 0GitHub stars: 3
- Spec WriterGenerates technical implementation spec, plan, AND an operational contract for one or more features based on PRD, codebase analysis, and iterative clarification. Produces contract.md (environment contract, quality gates, coverage manifest, observable criteria) consumed by implement-feature and evaluator. Supports batch mode for generating multiple features from the same wave in parallel.Votes: 0GitHub stars: 3
- Prd WriterGenerate complete PRDs (Product Requirements Documents) through iterative clarification. Use when: (1) Starting a new project and need structured requirements, (2) Creating product specifications with 9-section PRD format, (3) Defining product scope from a description or context files. Keywords: "prd", "product requirements", "create PRD", "generate PRD", "new product", "requirements document".Votes: 0GitHub stars: 3
- Pabx Design SystemFonte-da-verdade do design system do DRCALL PABX (Angular Material M3, aesthetic compacto/profissional). Use ao criar ou revisar qualquer UI do frontend — páginas, tabelas, dashboards, formulários, diálogos — para seguir tipografia, espaçamento, tokens de cor, padrões de página/tabela/dashboard e os anti-padrões proibidos. É também a base do gate styles-frontend e da verificação visual.Votes: 0GitHub stars: 3
- Monorepo Unit Test ValidatorAudits PABX monorepo unit tests (node-express, node-worker, python-fastapi apps outside apps/backend and apps/frontend) against the monorepo-unit-test-writer rules, auto-detecting the stack and producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected test conforms before resuming evaluation, or run directly by a user.Votes: 0GitHub stars: 3
- Implement FeatureImplements a feature autonomously based on its spec, plan, AND contract.md, committing one commit per phase, satisfying the contract's quality gates and observable criteria, writing progress.json, and reporting results against the feature's acceptance criteria. Delegates test writing to the matching test-writer skill (unit/integration/monorepo/e2e) by path/stack when the project fits, and falls back to writing tests itself otherwise.Votes: 0GitHub stars: 3
- Gate BuilderBuilds the deterministic quality-gate infrastructure for a project (typecheck, lint with zero-warnings, dependency/architecture checks, tests, dead-code, and a single runGate entry point) from the Deep Analysis Report (+ Architecture Analysis Report). Auto-detects greenfield vs. brownfield, proposes a gate plan for confirmation, then writes the configs/scripts and verifies each gate runs. The gates it builds are later declared in each feature's contract.md by spec-writer.Votes: 0GitHub stars: 3
- Deep AnalyzerPerforms an exhaustive, item-by-item deep analysis of every module, service, component, or endpoint listed in the Architecture Analysis Report (REQUIRED as input). Maps every implementation detail, data flow, contract, and failure mode, and produces a structured Deep Analysis Report. Analysis/reporting only — never modifies the codebase. In the SDD flow it runs after architecture-analyzer and feeds gate-builder.Votes: 0GitHub stars: 3
- Coupling MapAnswers which files to refactor first to reduce systemic risk, by crossing blast radius (how many modules stop working if this one breaks) against size. On first use it asks permission, installs its own tooling and writes a config by reading the project; on every run after that it executes a versioned script and reads only that script's JSON output, never the source tree again. Produces a standalone HTML report with a scatter chart, a ranked queue and structural detectors. Unlike architecture...Votes: 0GitHub stars: 3
- Architecture AnalyzerPerforms a comprehensive surface-area analysis of any codebase scope (a component, module, service, layer, or the full project). Inventories every entry point, dependency, pattern, and integration, scores complexity, and produces a structured Architecture Analysis Report consumed by the deep-analyzer skill. Analysis/reporting only — never modifies the codebase. In the SDD flow this is the first setup step for an existing (brownfield) project; it feeds deep-analyzer and then gate-builder.Votes: 0GitHub stars: 3
- Realistic CostShow what a 100% human-driven engineering team would have cost for this session — the full receipt with line items, coordination tax, grand total and per-role breakdown, or an export to pdf/png/html/md.Votes: 0GitHub stars: 4
- Realistic CostShow what a 100% human-driven engineering team would have cost for this session. Use /realistic-cost for the full receipt (line items, coordination tax, grand total, per-role breakdown), or /realistic-cost export pdf|png|html|md to export it.Votes: 0GitHub stars: 4
- Codex Remote ControlInspect and address Codex CLI sessions from inside Claude Code. Use when the user asks what Codex is doing, whether it is stuck or idle, how far along it is, what its rate limits are, which Codex sessions exist or are running, what a session was asked to do, what model or reasoning effort it is using, or asks to tell/instruct/message a Codex session. Sessions can be found by uuid, by working directory, or by words in their opening prompt. Also use for 'check on codex', 'is codex still running...Votes: 0GitHub stars: 3
- Light Venue Matching投稿定位与期刊/会议匹配。当用户问投哪个期刊/会议、要评估录用可能性/录用概率、做投稿规划时使用。根据论文质量、方向、创新程度、实验完整性、语言水平、作者背景和预算,推荐中文/英文期刊、SCI/SSCI/EI/CCF/核心、国际/国内会议。分析投稿难度、方向匹配度、审稿周期、版面费、以可核查信号做录用可能性定性分级(高/中/低,不编百分比)、是否适合本科生/弱导师资源、预警风险,给出冲刺/稳妥/保底分层选择。Votes: 0GitHub stars: 2