Helps choose a reusable application foundation by comparing actual workflow fit, ownership effort and alternatives to building from scratch.
business-project-foundations
Included files 4
SKILL.mdreferences/README.mdreferences/adoption-checklist.mdreferences/repositories.json
Helps you navigate an existing project by locating important files, system connections and the right place for a scoped change.
codebase-discovery
Included files 2
Shapes the smallest viable architecture around measurable requirements, explicit data ownership and the operational trade-offs your team faces.
architecture-planning
Included files 2
Converts a specification into ordered, reviewable delivery tasks with working user outcomes and explicit acceptance evidence.
task-breakdown
Included files 2
Implements server behavior in tested, coherent increments that preserve business rules, transaction integrity and visible failure states.
backend-implementation
Included files 2
Plans schema changes that preserve data and allow old and new application versions to coexist during transition.
database-migrations
Included files 2
Connects your application to other systems. Defines how they exchange data, handle errors and recover when a service is temporarily unavailable.
api-integration
Included files 2
Makes queued work safe to repeat and recover by treating duplicate delivery and partial completion as normal operational cases.
background-jobs
Included files 2
Connects logs, metrics and traces to concrete questions about failures, performance and user impact.
observability
Included files 2
Restructures legacy code in focused steps while recording current behavior and keeping intentional changes distinct from accidental regressions.
legacy-refactoring
Included files 2
Checks how your application handles sign-ins, forms, uploads and sensitive data. Helps prevent malicious input and unintended data exposure.
secure-coding
Included files 2
Builds tests for individual functions and complete workflows, helping catch errors and prevent previously fixed problems from returning.
testing-discipline
Included files 1
Keeps a code change complete but reviewable by following local conventions and limiting edits and dependencies to the requested outcome.
clean-changes
Included files 1
Maps the installed Laravel stack and actual project structure before choosing APIs, conventions or verification commands.
laravel-codebase-discovery
Included files 2
Uses existing Laravel conventions to give validation, authorization, business rules and HTTP handling clear responsibilities.
laravel-conventions
Included files 2
Designs expressive Laravel queries and model relationships with predictable events, memory use and data conversion.
laravel-eloquent
Included files 2
Enforces validated input, record permissions and tenant boundaries at Laravel's server-side entry points.
laravel-auth-validation
Included files 2
Verifies Laravel behavior with focused endpoint, permission and persistence tests using the project's existing test framework.
laravel-testing
Included files 2
Runs background work with explicit retries, durable outcomes and clean transaction and tenant boundaries.
laravel-queues-events
Included files 2
Plans schema changes and related writes around existing data, deployment order and recoverable transitions.
laravel-migrations
Included files 2
Improves measured database and response costs with bounded queries and correctly scoped cache entries.
laravel-performance-cache
Included files 2
Creates deliberate response contracts and efficient Inertia page data without exposing raw models or unnecessary relationships.
laravel-api-inertia
Included files 2
Makes scoped Laravel changes in verified steps while preserving application structure and observable contracts.
laravel-upgrade-refactoring
Included files 2
Places state, data and mutations across browser and server boundaries with explicit freshness and access rules.
react-next-server-boundaries
Included files 1
Checks frontend changes with repository tooling and real browser behavior, then reports precisely what the available evidence covers.
frontend-verification
Included files 2
Designs shared components with a small predictable interface and flexible composition while retaining native interaction behavior.
component-api-composition
Included files 1
Applies the same authorization rules to direct actions, queries, exports and background work, with denied access when context is missing.
server-side-policy-enforcement
Included files 1
Extends tenant isolation beyond database rows to caches, search suggestions, derived indexes and stored file access.
tenant-aware-cache-search-files
Included files 1
Strengthens application contracts at untrusted boundaries and represents domain states so invalid combinations are harder to construct.
type-safety-contracts
Included files 1
Interprets latency, achieved workload and server telemetry to explain bottlenecks and useful successful throughput.
performance-measurement-analysis
Included files 1
Assesses a specific open-source release against deployment needs, supply-chain exposure and license obligations.
oss-adoption-security-evidence
Included files 1
Checks implementation, dependencies and tests at a fixed revision to substantiate technical capability claims.
source-code-repository-inspection
Included files 1
Prioritizes dependency fixes from real advisory conditions and reachable application paths, minimizing unnecessary compatibility disruption.
security-advisory-remediation
Included files 1
Tests tenant boundaries adversarially using comparable data in two workspaces, including indirect relationships and shared infrastructure.
tenant-isolation-verification
Included files 1
Labels capability claims according to documentation, inspected source, executed experiments or explicit inference.
evidence-grading-research-verification
Included files 1
Tests a risky technical assumption in a small controlled experiment before committing to an implementation approach.
empirical-micro-benchmark-prototyping
Included files 1
Turns a technical recommendation into a concrete integration plan with local touchpoints, lifecycle boundaries and visible uncertainty.
integration-architecture-adoption-plan
Included files 1
Compares configuration, plugins, upstream work and forks against long-term maintenance and exit costs.
oss-extension-upstream-strategy
Included files 1
Adapts a small stable algorithm when its verified permissive license and limited dependencies make that appropriate.
oss-code-adaptation-attribution
Included files 1
Replaces architecture in complete, verifiable increments with clear ownership while old and new implementations coexist.
incremental-architecture-migration
Included files 1
Establishes whether a dependency upgrade actually works through lockfile review, reproducible builds and real integration paths.
compatibility-regression-verification
Included files 1
Helps choose between realistic solutions by considering development effort, ongoing maintenance and the consequences of changing course later.
trade-off-lifecycle-cost-analysis
Included files 1