All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 70,057
- 2,920
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 19,033–19,056 of 70,057 skills
- JournalWrite the numbered journal entry for a substantive session per Part 4 (raw notes, what surprised you, no narrative smoothing)Votes: 0GitHub stars: 2
- GateRun a stage-gate transition session per Part 7b (verify the gate leg by leg, reconcile the next stage's backlog, spec its first entry)Votes: 0GitHub stars: 2
- DiagramsDiagrams as source checked at the close: the routing test that picks a type, the drawing and truthfulness rules, altitude and layout, node evidence, the Design sketch at creation and the sync at closeVotes: 0GitHub stars: 2
- Design SurfaceThe design surface for UI projects (Part 5c): the design-heavy routing test, locked redlines as spec contracts, the bundle rule, design QA on the branch, /insights at gatesVotes: 0GitHub stars: 2
- CheckpointSurvey, sanity-check, spec-scoped commit, branch lifecycle, and the close checklist (Part 6)Votes: 0GitHub stars: 2
- Project WorktreesUse when creating, entering, debugging or removing a git worktree under `.worktrees/`, when a worktree URL returns 404 or 502, or when writing tooling that resolves a worktree's hostname, database or container name.Votes: 0GitHub stars: 2
- Project Site ReviewUse when working on the site-review widget or its backend, `public/site-review/widget.js`, anything under `src/Module/SiteReview/`, the site-review API routes, the dev harness, or `e2e/tests/site-review/`.Votes: 0GitHub stars: 2
- Project FrontendUse when working on `assets/styles/app.css`, Stimulus controllers, Turbo patterns, modal components, or any frontend visual behaviour.Votes: 0GitHub stars: 2
- Project BackendUse when working on PHP code under `src/`: forms, DTOs, Doctrine entities, controllers, commands, flash messages, or any PHP implementation work. For authorization see `project-authz`. For PHPUnit tests see `project-testing`.Votes: 0GitHub stars: 2
- Qa User MindsetUse when designing or running any UI verification — when every case in the pack could have been written by someone who has never watched a real person use software, and when a PASS came from typing perfect values in perfect order.Votes: 0GitHub stars: 6
- Qa Test DesignUse when choosing the two-to-five cases for a verification — what deserves the budget, which boundary earns its place, when an exploratory or security slot is warranted — and when a case pack is all happy path.Votes: 0GitHub stars: 6
- Qa Security ProbesUse when a ticket touches authentication, sessions, roles, money, personal data, uploads, or any server that trusts client input — the input an attacker sends on purpose, provable with the lane's own browser, API recorder and read-only database.Votes: 0GitHub stars: 6
- Qa IdentityUse when a /qa session starts on any ticket, before deriving a single expected value — and whenever a verdict is about to be written from reading code, from the dev's claim, or from what 'obviously' should happen.Votes: 0GitHub stars: 6
- Qa Combinatorial DesignUse when a feature has several independent inputs and the honest combination count is too large to run — roles by plans by locales, payment method by currency by coupon, OS by browser by network by font scale. Also when deciding which tier a test belongs in, and when a suite is red often enough that people re-run it instead of reading it.Votes: 0GitHub stars: 6
- Qa Case WritingUse when writing a test case record or filling in its result — when a title names a topic instead of a behaviour, steps hide the typed value, EXPECTED says 'works correctly', or ACTUAL says 'failed'.Votes: 0GitHub stars: 6
- Qa Accessibility VerificationUse when verifying any user interface — web or mobile — and the ticket, spec or design says nothing about accessibility. Also when an automated scan came back clean, when a design hands over only the default state, and when 'accessible' has to become a pass or fail with a number behind it.Votes: 0GitHub stars: 6
- Pm PrioritisationUse when choosing what the team does next and more than one thing is ready, when everything is labelled high priority, and when an item has been in progress longer than the others. Also when work is blocked on a person and the question is whether to wait, escalate or start something else.Votes: 0GitHub stars: 6
- Dev Testing CraftUse when deciding which tests to write for a change, how to name and structure them, what data they use, and how deep to go — and when an existing test is flaky, asserts nothing meaningful, or breaks on every refactor.Votes: 0GitHub stars: 6
- Dev Stack Nextjs PrismaUse when the project runs Next.js (App Router) with Prisma — when writing a route handler, server action, server/client component, Prisma query, transaction or migration, and when a page is slow, a query returns stale data, or a bulk update 'lost' rows.Votes: 0GitHub stars: 6
- Dev Security BasicsUse when code handles a request, a session, a secret, a file upload, a query built from input, or anything a user can address by id — and whenever the change touches auth, roles, money, personal data or deletion.Votes: 0GitHub stars: 6
- Dev Query PerformanceUse when a page or endpoint is slow, when a list grows, when an ORM sits between the code and the database, and when a query is written inside a loop. Also when pagination is added, when a cache is introduced, and when a fix is 'add an index' before anyone has looked at a plan.Votes: 0GitHub stars: 6
- Dev ObservabilityUse when a change ships something you will have to debug from the outside — a new endpoint, worker, integration or migration — and when the only answer to 'is it working?' is a screenshot. Also when an incident is being investigated and the logs do not say enough, and when an alert fires that nobody can act on.Votes: 0GitHub stars: 6
- Dev Mobile CraftUse when a ticket targets a phone or tablet — native Android or iOS, React Native, or Flutter. Especially when the change touches a screen's lifecycle, stored data, permissions, background work, or anything that must survive rotation, a lost network, or the OS killing the app. Also when deciding native vs cross-platform.Votes: 0GitHub stars: 6
- Dev Frontend CraftUse when a ticket touches the browser — a component, a screen, styling, client state, data fetching, routing, or a rendering strategy — and when choosing between the six or seven tools that all solve the same frontend problem. Also when a UI is 'done' but nobody has said which states it has.Votes: 0GitHub stars: 6