Brings a Laravel project that was scaffolded from CleaniqueCoders Kickoff up to the latest Kickoff baseline. Detects which Kickoff version a project started from (no marker exists — uses feature fingerprinting plus a git-date heuristic, then asks you to confirm), reads the latest Kickoff from the REQUIRED local install (composer global require cleaniquecoders/kickoff) and the original-version base from a git tag when available, and performs a category-grouped 3-way merge (base = original Kickoff, theirs = latest Kickoff, mine = your files) — falling back to a 2-way compare when the base cannot be obtained, never a blind overwrite. Patches packages, vendor:publish tags, navigation menu, config, Livewire and Blade components, layouts and theme, routes, bin scripts, CI workflows, docs, docker, and .env.example keys, while protecting project-owned code, .env, product config, and custom routes. Previews every change and applies only what you approve per category, then stamps a version marker so future runs are det
Senior SOC Analyst skill — stack-agnostic security operations for any web application. Auto-detects the project stack (Laravel/PHP, Node.js/Express, Python/Django/Flask/FastAPI, Ruby/Rails, Go, Rust, Java/Spring, .NET) then triages security alerts by severity (P1-P4) with MITRE ATT&CK categorization, investigates suspicious activity by tracing attack paths and correlating events, performs incident response with containment and eradication, actively remediates vulnerabilities in code (SQL injection, XSS, CSRF, insecure deserialization, auth bypass, file upload flaws, command injection, path traversal, SSRF, mass assignment), hardens applications proactively (security headers, rate limiting, input validation, dependency audit, secrets rotation), and generates incident reports with post-mortem documents. Use this skill whenever the user asks to analyze security issues, fix vulnerabilities, investigate incidents, harden their application, or audit for threats — including requests like "check for security vulnerab
SVG business card designer that takes contact details and brand preferences, then produces 12 front design concepts with optional back designs, interactive HTML preview galleries, individual card showcases with front/back flip animation, and print-ready SVG exports with bleed area and crop marks. Supports horizontal and vertical orientations, six layout styles (minimal, corporate, creative, elegant, bold, tech), multiple color schemes, QR code placeholders, social media icons, and logo integration. Use this skill whenever the user asks to design a business card, create a name card, make visiting cards, or says "design business card", "buat kad bisnes", "create name card", "reka kad perniagaan", "design kad nama", "I need a business card for X".
Pragmatic Domain-Driven Design for Laravel projects — business-first, not academic. Helps restructure Laravel apps from default flat structure into domain-based organisation with clear bounded contexts, domain layers (Models, Events, Contracts, Value Objects), application layers (Actions, Jobs, Services), and infrastructure layers (Registrars, Exports, Integrations). Focuses on what matters to the business: reducing OPEX through maintainable code, increasing velocity through clear ownership, and enabling teams to work independently on bounded contexts. Includes domain discovery interview, migration planner, scaffolding, service provider wiring, autoloading config, and architecture test updates. Use this skill whenever the user asks to restructure a Laravel app into domains, apply DDD, organise by business context, migrate to modular structure, or says "restructure app guna DDD", "nak buat domain-based structure", "organise code ikut business domain", "migrate to DDD", "buat bounded context", "refactor monolit
Complete API lifecycle management for Laravel applications — from OpenAPI design through governance and security hardening. Covers seven phases: design (OpenAPI 3.1 spec generation via interview), develop (controller/request/resource scaffolding with Sanctum/Passport auth), test (Pest API test generation with contract testing), deploy (versioned deployment with feature flags and zero-downtime migration), docs (auto-generated documentation with Scribe/Scramble), govern (breaking change detection, deprecation policy, API review), and security (OWASP API Top 10, input validation, rate limiting tiers). Use this skill whenever the user asks to design an API, generate OpenAPI specs, scaffold API endpoints, write API tests, deploy API versions, generate API documentation, review API changes, or harden API security — including requests like "design a REST API for X", "scaffold CRUD endpoints", "generate Pest tests for my API", "set up API versioning", "check my API for breaking changes", "generate API docs", "secure
Living document practice — Claude automatically updates CLAUDE.md whenever a user corrects a mistake, expresses a preference, a better pattern is discovered, or a gotcha is found during implementation. Use this skill whenever Claude is working inside a project that has a CLAUDE.md file, or whenever the user says things like "jangan guna X, pakai Y", "aku tak suka pattern ni", "ingat ni untuk lepas ni", "update CLAUDE.md", "catat ni", "tambah dalam CLAUDE.md", or any correction/preference that should persist across future sessions. Also triggers when Claude discovers an edge case or architectural insight worth preserving. The goal: CLAUDE.md should always reflect the current, correct, agreed-upon way of working — never let a correction live only in conversation history.
Multi-audience FAQ generator that researches a codebase (and optionally related repositories) end-to-end, then produces categorized FAQ documents for different stakeholder perspectives: business/executive, marketing/sales, project manager, administrator, developer, devops, and end user. Use this skill whenever the user asks to create FAQs, generate a knowledge base, build support documentation by audience, or produce stakeholder-specific Q&A documents — including: "generate FAQ for my project", "create FAQ for different audiences", "buat FAQ untuk projek ni", "FAQ for sales team", "developer FAQ", "devops FAQ", "admin FAQ", "knowledge base for my product", "support FAQ", "create Q&A docs", or "FAQ by persona".
Generates project roadmaps in Nasrul's exact style — always produces BOTH a ROADMAP.md (phase-based markdown with checkboxes, exit criteria, dependency map, and quick reference) AND a beautiful custom-styled HTML visual roadmap. Use this skill whenever the user asks for a roadmap, project plan, implementation plan, development phases, or says "buat roadmap", "plan for this project", "phase out the implementation", "apa first step", or "how should I build this". Also triggers when a CLAUDE.md exists and the user wants a matching roadmap, or when an existing roadmap needs updating based on new decisions. Always generates both files together — never just one. The HTML roadmap is styled uniquely per project type (not a generic template). Compatible with the nasrulhazim/claude-docs project structure.