BastiDood
- 26 skills
- 0 followers
- 6 hours ago last updated
- ▌ Git Commit · bastidood bundlePrepare cohesive staged Git commit slices and conventional messages without committing. Use when organizing pending changes into reviewable checkpoints.
- ▌ Code Style · bastidood bundleLanguage-agnostic code-design rules for explicit state, failure, ownership, and I/O boundaries. Use when implementing, refactoring, or reviewing code.
- ▌ Plugin Best Practices · bastidood bundleAgent-plugin design conventions for public outcomes, private implementation, and minimal packaging. Use when creating, restructuring, or reviewing agent-skill plugins.
- ▌ React Best Practices · bastidood bundleReact component conventions for explicit state ownership and data flow. Use when creating or reviewing React components, hooks, effects, or forms.
- ▌ Python Best Practices · bastidood bundlePython 3.13+ conventions for typed application and library boundaries. Use when writing or reviewing Python contracts, packages, validation, or async resource ownership.
- ▌ Svelte Best Practices · bastidood bundleSvelte 5 and SvelteKit conventions for explicit reactive ownership and component lifecycles. Use when creating or reviewing Svelte components, runes, context, or form actions.
- ▌ Zod Best Practices · bastidood bundleZod v4 conventions for owned wire contracts and explicit validation outcomes. Use when defining or reviewing Zod schemas or parsing untrusted data with Zod.
- ▌ Github Pull Request · bastidood bundleDraft and submit a reviewer-focused GitHub pull request with an approval gate. Use when turning finalized branch changes into a new PR.
- ▌ Testing Guidelines · bastidood bundleLanguage-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.
- ▌ Agent Skills Best Practices · bastidood bundleAgent-skill design conventions for focused scope, precise discovery, and progressive disclosure. Use when creating, restructuring, or reviewing `SKILL.md`-based skills.
- ▌ Valibot Best Practices · bastidood bundleValibot conventions for owned wire contracts and explicit validation outcomes. Use when defining or reviewing Valibot schemas or parsing untrusted data with Valibot.
- ▌ Adversarial Code Review · bastidood bundleIndependently review completed implementation against its agreed plan or specification. Use when closing out feature work, a bug fix, or another implementation run.
- ▌ Bulletproof Functions · bastidood bundleLanguage-agnostic rules for honest, testable function boundaries. Always use when planning, writing, reviewing, or critiquing functions and abstractions.
- ▌ Drizzle Orm Best Practices · bastidood bundleDialect-aware Drizzle ORM conventions for safe query, mutation, and transaction boundaries. Use when writing or reviewing Drizzle schemas, queries, transactions, or raw SQL.
- ▌ Presentation Creator · bastidood bundleCreate and visually verify a Basti-styled PowerPoint deck from an approved Markdown plan. Use when executing an approved slide-by-slide plan, not when planning or rewriting the narrative.
- ▌ Presentation Planner · bastidood bundleTurn source material into an implementation-ready Markdown presentation plan. Use when planning slide narrative, notes, visuals, and transitions without creating the deck.
- ▌ Shadcn Svelte Best Practices · bastidood bundleshadcn-svelte and Bits UI conventions for accessible primitive composition and customization. Use when creating, wrapping, restyling, or reviewing those components.
- ▌ Better All Best Practices · bastidood bundle`better-all` conventions for dependency-aware async task graphs. Use when defining `all` or `allSettled` graphs or converting staged async work with task dependencies.
- ▌ Typescript Best Practices · bastidood bundleTypeScript conventions for precise contracts and valid program states. Use when writing or reviewing TypeScript types, state models, optional values, or untrusted boundaries.
- ▌ Github Pull Request Comments · bastidood bundleVerify and triage unresolved GitHub PR feedback into amendment plans or evidence-backed rebuttals. Use when planning responses to review comments.
- ▌ Tanstack React Query Best Practices · bastidood bundleTanStack Query conventions for cache-backed React server state. Use when creating or reviewing React queries, mutations, query keys, or cache updates.
- ▌ Tanstack React Table Best Practices · bastidood bundleTanStack Table v9 conventions for stable React table schemas and instance behavior. Use when creating or reviewing React tables, columns, metadata, or rendering.
- ▌ Open Telemetry Best Practices · bastidood bundleLanguage-agnostic OpenTelemetry conventions for queryable signals and explicit operational outcomes. Use when adding or reviewing spans, structured logs, attributes, or exception recording.
- ▌ Tanstack Svelte Query Best Practices · bastidood bundleTanStack Query conventions for reactive, cache-backed Svelte server state. Use when creating or reviewing Svelte queries, mutations, query keys, or cache updates.
- ▌ Tanstack Svelte Table Best Practices · bastidood bundleTanStack Table v9 conventions for static Svelte table schemas and reactive instance data. Use when creating or reviewing Svelte tables, columns, metadata, or rendering.
- ▌ Vertically Sliced Feature Modules · bastidood bundleFeature-first module architecture for cohesive ownership, composition, and promotion boundaries. Use when designing, moving, or reviewing feature and package structure.