bioeksen-sds
Shared BioEksen conventions and practice: API design, auth, logging, configuration, commits, testing, database, reviewing, CI, and Next.js
Plugin bioeksen-sds from marketplace bioeksen-skills in TarikEren/bioeksen-ai-skills. Commands read from the repo's manifest — 1 month ago.
What it installs
Skills (12)
sds-api-designBioEksen API design conventions. Use when designing, reviewing or implementing an API — an HTTP endpoint, or a server-side function an app's own UI calls, such as a server action — and when writing a call to another service — timeouts, retries, circuit breakers and idempotency.
sds-authBioEksen authentication and authorization conventions. Use when protecting an endpoint, deciding which credential a caller needs, validating a token, or choosing the error code for a rejected request.
sds-ciBioEksen CI, runner, delivery and AI task conventions. Use when writing, changing or proposing a forge workflow, registering or configuring a runner, setting up deployment, changing a container image or a local-development compose file, preparing a release, finding out why a run failed, or delegatin
sds-commitBioEksen conventional commit format. Use when writing or amending a commit message, minting its Change-Id, reviewing commit history, or deciding a release version from a set of commits.
sds-configBioEksen configuration conventions. Use when adding, reading or validating a configuration value, an environment variable or a secret, or deciding what an app does when one is missing or unusable.
sds-databaseBioEksen database conventions: one source of truth for the schema and a drift check, modelling with constraints that enforce the specification's invariants, forward-only migrations that are safe on a live database (expand and contract, locks, backfills, no silent data loss), transactions and concurr
sds-loggingBioEksen logging and error code conventions. Use when adding log statements, choosing a severity or log type, defining or returning an error code, or wiring an app to the log aggregator.
sds-nextjs-backendBackend conventions for a Next.js App Router project in TypeScript: route handlers, server actions, a server-only data access layer (services and repositories), Zod validation at every boundary, authentication and authorisation, safe errors and logging, transactions. Rules for type-safe, secure and
sds-nextjs-frontendFrontend conventions for a Next.js App Router project styled with HeroUI v3 and Tailwind CSS v4 over a Fluent-style brand palette. Rules for type-safe, secure and modular UI code: the server/client trust boundary, HeroUI components only, palette and semantic tokens, WCAG 2.1 AA contrast, UI copy fro
sds-planningBioEksen specifications and build planning. Use when writing, changing or reviewing a service's specification — its decisions, build items and acceptance criteria — when a rule is missing and has to be asked, when ordering the build into stages with exit criteria, and when writing a stage's plan for
sds-reviewingReviewing code changes and recording the review in a BioEksen service. Part A covers the review: an independent reviewer's stance, scope and base commit, who reviews what (application code, or data changes), the rules to review against, passes in priority order (security, correctness, type safety, m
sds-testingBioEksen test-first development and testing practice. Use before writing or changing behaviour in a BioEksen service — a feature, a bug fix, an endpoint, a log statement, an auth check — to write the failing test first and find the contract test a shared convention requires; and when writing, changi
Maintain bioeksen-sds?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.