Development

Programming, frameworks, implementation, frontend, backend, and app development

skills in category: 65,853
pages available: 2,744

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 browser

Browse development skills

Showing 12,145–12,168 of 65,853 skills

Map Skill EvalAEvaluate a $map-* skill's trigger accuracy and cost. Use when asked to measure skill trigger accuracy, run an eval-set, or check token/duration cost via `mapify skill-eval`. Do NOT use to plan or implement; use map-plan or map-efficient.developmentrustgoVotes: 0GitHub stars: 157
Map ReviewAInteractive 4-section code review using Monitor, Predictor, and Evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.developmentpythonrustVotes: 0GitHub stars: 156
Map ResumeAResume an interrupted MAP workflow from .map/<branch>/step_state.json checkpoint. Use when returning after context exhaustion, /clear, or a session crash mid-workflow. Do NOT use to start new work; use map-plan or map-efficient.developmentpythonrustVotes: 0GitHub stars: 156
Map ReleaseAExecute the mapify-cli package release workflow with validation gates and PyPI publication. Use when shipping a new MAP Framework release. Do NOT use for ordinary feature work; use map-efficient.developmentrustshellVotes: 0GitHub stars: 157
Map Prd ReviewAUse when reviewing a PRD, product brief, feature brief, or requirements document before planning or engineering handoff. Produces an evidence-backed 0-10 readiness score, strengths, weaknesses/risks, and uncovered edge cases across 13 dimensions. Do NOT use as a substitute for $map-plan, for code review, or for tiny engineering tasks with no PRD.developmentpythonrustVotes: 0GitHub stars: 156
Map PlanAARCHITECT phase - decompose complex tasks into atomic subtasks with research, spec, and branch-scoped plan artifacts under .map.developmentpythonrustVotes: 0GitHub stars: 157
Map Memory NowAFinalize cross-session memory on demand; --finalize-all sweeps every dirty scratch. Use when ending a long session or before switching branches. Do NOT use for routine edits — finalize auto-runs at next SessionStart. Requires Codex CLI + git.developmentpythonrustVotes: 0GitHub stars: 156
Map LearnACapture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want audited rules written to `.map/learned/` and promoted into the managed MAP section of `AGENTS.md`. Do NOT use during active implementation.developmentpythonrustVotes: 0GitHub stars: 157
Map FastAMinimal MAP workflow for small low-risk changes (40-50% token savings, no Predictor/Reflector). Use when the change is small, low-risk, and learning is not needed. Do NOT use for risky or complex work; use map-efficient.developmentrustgoVotes: 0GitHub stars: 157
Map ExplainAExplain code, a diff, or the whole project the way a knowledgeable colleague would — result and main scenario first, then participants, flow, mechanisms, rules and constraints in progressive depth, with ASCII diagrams; for a PR or diff, exactly the change against the base with new behavior separated from existing context, documentation clarifications and unimplemented plans. Use when learning unfamiliar code, onboarding to a system, or auditing what a PR really does.developmentrustgoVotes: 0GitHub stars: 157
Map EfficientAState-machine MAP execution workflow for Codex. Use when implementing an approved MAP plan end to end, resuming from branch MAP task_plan or step_state.json artifacts, or running non-trivial multi-subtask work. Use map-fast for tiny one-shot edits.developmentpythonrustVotes: 0GitHub stars: 157
Map DebugAStructured MAP debugging via decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C extensions, intermittent or load-dependent failures (e.g. 500s under load), data-corruption bugs that only appear in production, scripts or hooks that silently exit or produce no output, and...developmentpythonrustVotes: 0GitHub stars: 157
Map CheckARun quality gates (lint, types, tests) and verify MAP workflow completion. Use when user asks to run checks, validate a workflow, or confirm a MAP run is done. Do NOT use to plan or execute new tasks; use map-plan or map-efficient.developmenttypescriptpythonVotes: 0GitHub stars: 156
Map AutoASingle-entry autonomous autopilot: routes a task through the existing MAP workflows via `route_task`, then drives the selected chain (map-plan -> map-efficient -> map-check -> map-review, as routed) end-to-end to a committed feature branch in one session, auto-approving routine workflow-control holds and hard-stopping on dangerous_action/safety_guardrail holds. Use when you want the whole pipeline to run unattended from a single task description, without babysitting phase-by-phase invocation....developmentpythonrustVotes: 0GitHub stars: 157
Map ArchitectureAOpt-in proactive architecture-deepening report: ranks codebase areas by recent git hotspot and design friction, generates a ranked Markdown+Mermaid candidate report under .map/<branch>/architecture-report/, then waits for you to pick one candidate before any code changes. Use periodically, or when agentic complexity feels like it is accelerating, to find where a deeper module would buy future leverage. Do NOT use for current-diff code review — use $map-review; do NOT use to plan or implement ...developmentrustgoVotes: 0GitHub stars: 157
Rbac Permissions BuilderAImplements role-based access control with permission matrix, route guards, policy functions, and UI permission hints. Provides middleware/guards, helper utilities, test suggestions, and permission checking patterns. Use when building "RBAC", "permissions", "access control", or "authorization".developmenttypescriptexpressVotes: 0GitHub stars: 78
OpencliAOpenCLI — Make any website or Electron App your CLI. Zero risk, AI-powered, reuse Chrome login.developmentjavascripttypescriptVotes: 0GitHub stars: 78
Frontend PatternsAFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.developmenttypescriptgoVotes: 0GitHub stars: 78
Coding StandardsAUniversal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.developmentjavascripttypescriptVotes: 0GitHub stars: 78
Backend PatternsABackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.developmenttypescriptgoVotes: 0GitHub stars: 78
Api DesignAREST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.developmenttypescriptpythonVotes: 0GitHub stars: 78
Ios Signing DoctorADiagnose and fix iOS code-signing, provisioning, and entitlement failures — the "no signing certificate / no profiles / doesn't match / get-task-allow" family, using codesign/security to inspect what's actually signed. Use when an archive, upload, or CI build fails on signing.developmentgobashVotes: 0GitHub stars: 41
Android Signing SetupASet up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.developmentgokotlinVotes: 0GitHub stars: 41
Android ScaffoldAScaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.developmentpythongoVotes: 0GitHub stars: 41