Development

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

skills in category: 62,644
pages available: 2,611

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 9,913–9,936 of 62,644 skills

SetupAFirst-run Eklavya setup — check prerequisites, create the database, choose how hard it pushes, and say what memory does.developmentrustgoVotes: 0GitHub stars: 9
ProgressAShow the Eklavya mastery map — which projects you have been learning on, what those sessions actually taught, what you skipped, and what is due for review.developmentgoVotes: 0GitHub stars: 9
PackAWrite or edit an Eklavya concept pack — a JSON file of concepts, tiers and prerequisites that adds a domain, or a team's own codebase, to what Eklavya can quiz on.developmentrustgoVotes: 0GitHub stars: 9
Eklavya DashboardAHow Eklavya's dashboard (`eklavya dashboard`) is built and how to change it — the four workflows (Learning, Memory, Artifacts, Settings) and their registry, the one JSON payload plus the project inventory, the URL-driven hash router and its legacy redirects, the hand-rolled SVG charts, the table/pagination helpers, and the checks a change has to pass. Use whenever adding, editing or debugging anything in mcp/src/dashboard.ts or mcp/src/assets/dashboard.html, or when a request mentions the das...developmentrustgoVotes: 0GitHub stars: 9
Rseng TestingACovers how to test research software: choosing test types and levels (unit, integration, system, regression, property-based, golden-master), test frameworks and coverage, TDD, validating analysis code against reference cases, and taming CI testing matrices across compilers, platforms and dependency versions. Use when the user asks how to write tests, set up pytest/testthat/JUnit, decide what to test, raise or interpret code coverage, do test-driven development, or when a CI matrix is explodin...developmentpythonrustVotes: 0GitHub stars: 20
Rseng Software DesignACovers designing research software: modularity and separation of concerns, interfaces and coupling, growing from script to package, the rule of three and the reuse ladder, architecture styles for research systems (pipeline, layered, plugin, services), quality-attribute trade-offs, visual design documentation (C4, Mermaid, PlantUML diagrams-as-code) and architecture decision records. Use when starting non-trivial research software, when a script has grown past easy understanding, when the user...developmentgotestingVotes: 0GitHub stars: 20
Rseng Management PlanningACovers planning research software work: writing and maintaining a Software Management Plan (SMP), and choosing programming languages, tools, and infrastructures for a project. Use when the user wants to write or review an SMP, plan how software will be developed, maintained, shared, and preserved, needs the software sections of a proposal or funder template, wants to decide which language or framework to start a project in (Python, C++, R, Julia, Rust, Fortran, JavaScript), pick a project tem...developmentjavascripttypescriptVotes: 0GitHub stars: 20
Rseng Language GuidesACovers language-specific research software practice: per-language conventions for Python, R, JavaScript/TypeScript, C/C++, Fortran, Rust and Bash - setup, development environments, style standards, packaging, testing, quality assurance, optimization, logging, documentation and dependency management. Use when the user asks which tools or conventions to use FOR A SPECIFIC LANGUAGE in research software (e.g. Python packaging, R style, C++ QA, Fortran tooling, Rust starting points, shell scriptin...developmentjavascripttypescriptVotes: 0GitHub stars: 20
Rseng Citation MetadataACovers making research software citable and contributors credited: writing CITATION.cff, describing software with CodeMeta (codemeta.json), minting DOIs and ORCIDs, and tracking contributors of every kind. Use when the user asks how to make software citable, add CITATION.cff or codemeta.json, obtain a DOI, ensure contributors get credit, or mentions CFF, CodeMeta, ORCID, CRediT or persistent identifiers. Use PROACTIVELY when generated code draws on a publication, website or existing code (cre...developmentpythonrustVotes: 0GitHub stars: 20
Worklog QueryAUse when the user asks about past Claude Code work in a way that goes beyond a single day -- "what did I do last week", "compare Tuesday and Thursday", "show me everything on project X this month", "when did I fix that redirect URI bug", "how much did I work on the auth stuff". Daily worklog entries (notes/{date}.md) are already generated automatically by hooks; this skill is only for custom, cross-day, cross-project, or tag-filtered queries against what has already been captured and summariz...developmentpythongoVotes: 0GitHub stars: 8
Straighten EdgesARemove staircase edges from raster-derived parcels with a junction graph and deviation test, preserving shared boundaries.developmentgonodeVotes: 0GitHub stars: 8
Raster To PolygonsARAM-safe raster to polygon conversion for large rasters: tiling with overlap, components, seam merge, min-area filter, resume.developmentpythongoVotes: 0GitHub stars: 8
Review StandardsAMerge criteria per stack (TypeScript/Next.js, Python, .NET, Expo) plus cross-cutting rules on secrets, contracts, migrations, tests, CRS. Apply during code review or before a PR.developmenttypescriptpythonVotes: 0GitHub stars: 8
ObservabilityALogging, metrics and alert conventions per service. Apply when adding logging, telemetry or alerts.developmentnextjsflaskVotes: 0GitHub stars: 8
Release ChecklistAPre-release verification for the Expo app: typecheck, tests, bundle check, EAS profile, versions, permissions, model asset, OTA.developmentrustapiVotes: 0GitHub stars: 8
App RulesANon-negotiable rules for the farmer Expo app: RTL-safe layout, single text component, Latin digits, server-truth numbers, secure storage, signing parity.developmentgogitVotes: 0GitHub stars: 8
Api ContractAEnvelope and DTO contract between the Expo app and the .NET farmer API: success from body, verbatim field names, refresh, error mapping, parity checks.developmentapiVotes: 0GitHub stars: 8
Study DashboardAAudit an existing GIS dashboard (pages, layers, endpoints, freshness, performance, UX) into docs/DASHBOARD.md.developmentbashapiVotes: 0GitHub stars: 8
New LayerAPublish a map layer end to end: table, display view, tile service, dashboard config, legend, smoke test.developmentpythonapiVotes: 0GitHub stars: 8
Slice ConventionsALayout and rules for the .NET minimal-API vertical slices and the Next.js dashboard routes — Endpoints/Models/Service per feature, proc-backed data access, policy gating, rate-limit policies, tests on SQLite, frontend route-local libs. Apply when adding or changing a feature in the dashboard API or web app.developmentrustsqlVotes: 0GitHub stars: 8
Schema PostureAHow database changes are made against the live SQL Server — never migrations; hand-run additive scripts with XACT_ABORT, verification SELECTs, a byte-verbatim ROLLBACK twin, an applied-to log and owner authorization. Apply to any SQL, DDL, index, proc or data change.developmentsqltestingVotes: 0GitHub stars: 8
Contract CheckACheck the mobile app's API client types against the .NET API's DTOs and envelope, both directions, and list every mismatch. Use when either side changes or before a mobile release.developmenttypescriptc#Votes: 0GitHub stars: 8
DockerizeAProduction Dockerfile and compose for Next.js, Flask/GDAL, .NET or pipeline workers.developmentpythonnextjsVotes: 0GitHub stars: 8
Deploy ProfilesAHow each service runs locally and in the cloud (Firebase App Hosting, Vercel, Hugging Face Spaces, EAS, Docker, AWS) with commands, config, env sources, health checks, rollback. Apply to deploy, hosting, environment or AWS tasks.developmentpythonsqlVotes: 0GitHub stars: 8