AdesolaOdubiyi
- 21 skills
- 0 followers
- 2 hours ago last updated
- ▌ Tdd · adesolaodubiyi bundleTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
- ▌ Grilling · adesolaodubiyiOne-question-at-a-time design grilling. Ask a single targeted question, wait for the answer, push back like a senior engineer if the answer introduces risk or ambiguity, then continue. Use inside design sessions to stress-test decisions before locking them.
- ▌ Implement · adesolaodubiyiStructured implementation loop for any non-trivial feature, tool, or change. Use when you have a spec, ticket, or clear requirement and need disciplined execution: confirm context, search best practices with cited sources, lock architecture before coding, TDD vertical slices, review loop, ship. Use instead of coding directly whenever the feature touches more than one layer or requires any design decision.
- ▌ UX Product · adesolaodubiyiActivate when designing, building, or reviewing any user-facing feature, interaction, screen, or flow. Forces product thinking before and during implementation.
- ▌ Review Loop · adesolaodubiyiIterate on AI PR review feedback until all comments are addressed or the cycle limit is hit. Use when the user says "loop on review", "address review comments", "keep going until reviewer is happy", "iterate on PR feedback", or any request to repeatedly fix AI reviewer comments. Works with any AI reviewer (GitHub Copilot, Cursor, Sidekick, etc.) — not tied to a specific tool.
- ▌ Readme Writer · adesolaodubiyiWrite or rewrite a README for any project. Activate when user says: write a readme, create a readme, update the readme, document this project, write docs for this, readme for this.
- ▌ Systems Design · adesolaodubiyiActivate when designing features, components, data flows, APIs, or system architecture at any scale. Also activate when refactoring large sections of code where the structure itself is in question, or when a proposed approach needs rigorous evaluation before implementation. Trigger phrases: "design this", "help me think through", "how should I architect", "what's the best approach for", "design review", "is this a good design", "let's design", "system design"
- ▌ Design To Build · adesolaodubiyi bundleEnd-to-end workflow for designing, architecting, and safely building any non-trivial feature, refactor, or system. Runs a structured grill session to surface constraints and lock in decisions, produces CONTEXT.md (domain language), KNOWLEDGEBASE.md (engineering + product memory), and docs/ARCHITECTURE_PLAN.md + docs/PROGRESS.md, then guides phased TDD implementation with clean code review, pre-merge review, and security audit at each gate. Use when starting a large feature, significant refactor, or anything that requires design decisions before a single line of code is written.
- ▌ Grill With Docs · adesolaodubiyi bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ Python Top Down · adesolaodubiyiEnforce Python top-down module structure: public API and high-level logic first, private helpers and low-level implementation at the bottom. Use when writing, reviewing, or refactoring any Python module — especially when the user mentions top-down structure, module ordering, readability, or asks why a function is hard to find. Also use proactively when generating new Python modules with more than 3 functions.
- ▌ Security Auditor · adesolaodubiyi bundleAdversarial multi-pass security audit of any codebase. Activate when user says: security audit, audit this codebase, security review, find vulnerabilities, audit this, security check, run the auditor, check for vulnerabilities, adversarial review.
- ▌ Post Rebase Verify · adesolaodubiyiRun after any rebase that required manual conflict resolution. Checks that intentional additions survived --ours/--theirs resolution and that structured files (package manifests, configs, interfaces) are consistent. Catches the class of silent-drop failures that only surface when a reviewer asks "where's the TODO?" or a build fails. Trigger on "post-rebase", "after rebase", "verify rebase", "check rebase", or whenever you just resolved rebase conflicts.
- ▌ Clean Code Reviewer · adesolaodubiyiCode cleanliness, maintainability, and best practices review before any merge. Activate when user says: review this code, cleanliness check, code quality review, check my code, review before merge, is this clean, maintainability review.
- ▌ Architecture And API · adesolaodubiyiActivate when planning module structure, designing APIs, refactoring system boundaries, or making changes to any externally consumed interface. Prevents unnecessary complexity and protects contract stability.
- ▌ Debugging Systematic · adesolaodubiyiStructured diagnosis loop for hard bugs, silent failures, and performance regressions. Activate when user says: debug this, diagnose this, something is broken, this is throwing, this is failing, data not persisting, status stuck, bug report, performance regression, this isn't working.
- ▌ Technical Docs Writer · adesolaodubiyiWrite or update technical documentation for a codebase or module. Activate when user says: document this codebase, write technical docs, document this module, write a module readme, document the architecture, write docs for this service, create architecture docs, document this system.
- ▌ Frontend Visual Design · adesolaodubiyi bundleDesign and implement sleek, human-feeling UI that doesn't read as AI-generated. Use when redesigning or building the visual layer of a UI (palette, typography, layout chrome, motion) — as opposed to `ux-product`, which handles interaction/product thinking. Trigger on "redesign the UI", "make this look less AI", "mock up a design direction", "pick a visual style".
- ▌ Python Type Discipline · adesolaodubiyiActivate when generating or refactoring Python code that involves function signatures, models, interfaces, or typing decisions.
- ▌ Backend Pre Merge Reviewer · adesolaodubiyiRigorous backend security and quality review before any merge or commit. Activate when user says: review this, pre-merge check, backend review, check before merging, audit this change, review my backend code.
- ▌ Frontend Pre Merge Reviewer · adesolaodubiyiStaff-level frontend pre-merge review for production-sensitive user-facing apps. Pair with ux-product to verify product decisions are reflected in code; use web search for current framework best practices and failure modes (TypeScript/React typical). Activate when user says: frontend review, pre-merge check UI, review my React change, check this frontend PR, UX implementation review.
- ▌ Improve Codebase Architecture · adesolaodubiyi bundleFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.