ceilidhboy
- 30 skills
- 0 followers
- 9 hours ago last updated
- ▌ Bug Fix · ceilidhboyActivate when user reports a bug, broken feature, failing behaviour, or says 'fix this', 'not working', 'doesn't work', 'error', 'regression'. ALWAYS before writing any fix — red-green only.
- ▌ Pr Review · ceilidhboy bundleReview a GitHub pull request by orchestrating reviewer + oracle sub-agents directly from the orchestrating session, consolidating their findings into a single report, and asking for approval before posting. Use when user says "review PR
- ▌ HTML Output · ceilidhboy bundleHTML output generator for output that would benefit from being presented in a visually rich document. Use when communicating architectural plans, design options, code review summaries, workflows, comparisons, novel concepts, color choices, or any information that benefits from visual illustration — inline SVG diagrams, color swatches, structured comparison grids, interactive controls. Not needed for simple lists, linear text, or straightforward data using well-understood terminology.
- ▌ Tdd Laravel · ceilidhboy bundleTest-driven development with red-green-refactor loop using Pest PHP. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, asks for test-first development, or needs guidance on writing testable code with Pest.
- ▌ Adr Creation · ceilidhboy bundleCreates and maintains dual-format ADRs — Markdown (source of truth for agents) and HTML (rich explainer for humans with diagrams). Keeps both formats in sync on updates. Use when user says "create an ADR", "document this decision", "write an ADR", "ADR for X", or when creating or updating a file in docs/adr/.
- ▌ Write A Skill · ceilidhboyCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ▌ Action Pattern · ceilidhboyCreating and using action classes to encapsulate business logic. Actions replace traditional Service classes with reusable, composable, single-responsibility classes that follow a consistent `execute()` convention.
- ▌ Settings System · ceilidhboyMulti-tenant polymorphic settings system with agency-scoped records and global fallback chain. Create, read, update settings records. Use when working with App\Models\Setting, App\Enumerations\SettingType, the settings table migration, the polymorphic settings system, or the fallback chain (agency-specific → global default). Also use when integrating third-party services (Xero, Stripe, etc.) that need per-agency configuration storage.
- ▌ Troubleshooting · ceilidhboyGeneral troubleshooting guidance that routes to specific backend or frontend troubleshooting skills.
- ▌ Project Bootstrap · ceilidhboy bundleUse when setting up a new Laravel + Inertia + React project, onboarding a new project to company standards, or told to "apply company tooling" or "standardise tooling". For existing/deployed projects that already have legacy tooling, see the formatting-enforcement skill instead.
- ▌ Serena Conventions · ceilidhboyUse when navigating code with Serena tools — finding symbols, reading method bodies, inserting code, or deciding between Serena and context-mode for code tasks. Covers correct parameter shapes, the Serena-first workflow, and when to fall back to context-mode.
- ▌ Serena MCP Selection · ceilidhboyRules for selecting between the LSP and JetBrains Serena MCP servers when both are configured. Default to LSP unless the user explicitly opts in to JetBrains.
- ▌ Unexpected Situations · ceilidhboyStop and consult the user when encountering unexpected situations, multiple failed attempts, or out-of-scope work. Use when things aren't plain sailing, when encountering unexpected behavior, when multiple workarounds fail, or when work appears to exceed task scope.
- ▌ Wayfinder Conventions · ceilidhboyProject routing conventions and patterns. Complements the Laravel Wayfinder skill with project preferences for actions over routes.
- ▌ Creating Pull Requests · ceilidhboyCompany pull request workflow and branch policy. Use when user says "create a PR", "make a pull request", "open a PR", or when managing GitHub pull requests for company projects.
- ▌ Formatting Enforcement · ceilidhboy bundleRetrofit formatting enforcement onto an existing Laravel project that has accumulated drift (badly formatted code committed under an always-green lint CI) or legacy tooling conflicts (Prettier vs Biome). Use when told to "harden linting", "fix formatting drift", "stop formatting merge conflicts", "apply the quality pipeline", or when an existing project's CI uses fix-mode formatters (pint/biome/prettier --write) that never fail. For new projects, use project-bootstrap instead.
- ▌ Github CLI Workarounds · ceilidhboyWorkarounds for shell escaping issues when using the GitHub CLI (`gh`) for creating issues, gists, and pull requests with content containing special characters like `$`, backticks, or quotes. Use when creating GitHub issues, gists, or pull requests where content contains `$variables`, backtick-enclosed code, or multi-line bodies that cause shell parsing errors.
- ▌ Routing And Controllers · ceilidhboyCreating controllers, registering routes, and understanding how routes map to Wayfinder TypeScript actions.
- ▌
- ▌ Monthly Report Generator · ceilidhboy bundleGenerate monthly development reports for clients using git history, PRs, and ADRs. Research commits/PRs/ADRs for a given repo and date range, then produce a plain-English HTML report for non-technical clients plus a Markdown version for email. Optionally update the project wiki. Use when user says "monthly report", "client report", "development report", "report for [client]", "summarise work", or asks you to document work done over a period.
- ▌ Pest Testing Conventions · ceilidhboy bundlePest 4 testing conventions, workflows, and troubleshooting for Laravel projects. Activates when writing or debugging tests, working with browser/smoke/architecture tests, handling test output issues (PAO mode, crash diagnostics), setting up datasets or mocking, and following project conventions for assertions, higher-order expectations, and test organization.
- ▌ Troubleshooting Frontend · ceilidhboyTroubleshooting TypeScript, React, and frontend-related errors.
- ▌ Inertia React Conventions · ceilidhboyReact component architecture and project conventions for Inertia.js v2 applications. Covers directory structure, structural vs markup components, DRY patterns, prop naming, and project-specific patterns.
- ▌ Boost Documentation Search · ceilidhboySearch Laravel Boost documentation effectively when Boost-specific information is needed.
- ▌ Single Task Responsibility · ceilidhboyRecognize when task implementation violates Single Responsibility Principle and stop to consult the user. Use when implementing a task and discovering you're addressing multiple distinct responsibilities.
- ▌ Writing Skills Readme First · ceilidhboyBefore creating any new skill, check the user's personal skills repo if they have one. Use the write-a-skill skill for the template. This is the mandatory starting point for all skill creation work.
- ▌ Spatie Data Transfer Objects · ceilidhboyCreating and composing Spatie Laravel Data transfer objects for backend-to-frontend communication with automatic TypeScript type generation.
- ▌ Component Composition Patterns · ceilidhboyBuilding reusable components through composition using generic base components with specific wrapper components that provide styling, configuration, and domain-specific behavior.
- ▌ Javascript Typescript Conventions · ceilidhboyProvides JavaScript and TypeScript coding conventions including casing rules, naming patterns, and best practices for variables, constants, components, and types. Use when writing or editing .ts, .tsx, .js, .jsx files, creating React components, or working with TypeScript types.
- ▌ Refactor Comments That Are Code Smells · ceilidhboyScans code for comments that explain what code does and refactors them using the action pattern or extracting to methods. Use after writing or editing any code.