agentic-stuff

User's conventions and patterns for native macOS Swift apps. Use when working on a Swift or macOS app project

Streamlined workflow for implementing features with ait issue tracking. Handles: reading project context, checking outstanding work, planning new features, creating ait issues, and implementing with proper acceptance criteria checking. Use when starting a new session or beginning work on a feature.

One-stop review after feature work, or for a whole codebase. Runs deterministic checks (section ordering, arch conventions) free of charge, then fresh-eyes reviewer agents. Covers team conventions, test quality, complexity, security, and Livewire/Flux patterns - plus runtime checks (a11y, cold UX probe) when UI changed. Also has a quick mid-session sanity-check mode ("this seem ok?").

Turn a settled feature discussion or plan document into consultant-ready ait issues — an initiative/epic vision document plus implementation specs a fresh agent could pick up cold, tomorrow. Use towards the end of a feature conversation ("let's get this into ait"), or when converting a plan file. Also the knowledge base for the plan-to-ait agent. For driving the ait CLI itself, see the ait skill.

Flesh out a terse ait issue into a detailed plan. Takes a vague "reminder to self" issue and explores the codebase to produce a proper plan document ready for plan-to-ait.

Conversational 'second pair of eyes' that finds reachable-but-dormant code in long-lived codebases — jobs, mailables, listeners, routes, commands that are still wired up but probably defunct — gathers concrete grep/git/telemetry evidence, and asks the developer 'cruft or keep?'. The developer is the oracle; the skill never deletes. Use when asked to audit or find dead/unused/dormant/defunct code, to 'cruft or keep', to spring-clean a codebase, or to check whether a specific mailable/job/route/command is still used.

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

Capture faithful, full-page reference screenshots of an existing web app's UI before or during a frontend migration (for example Bulma/Bootstrap + Vue to Livewire/Flux + Tailwind), so the rebuilt UI can keep a familiar 1:1 mapping for end users who treat the app as a tool. Use this whenever the user wants to screenshot or snapshot the current UI, capture every admin/staff/student page for reference, grab login-only or role-gated pages (including via impersonation), or says things like "screenshot the old UI", "capture the current pages", or "reference shots for the migration". Drives a real browser with Playwright rather than the in-browser Chrome screenshot tool, which only captures the viewport and cannot save full pages to disk. Tuned for Laravel apps but the capture technique applies to any web app.

Walk a developer through upgrading a production Laravel app from Livewire v3 to v4. Use when the user asks to upgrade Livewire, mentions the Livewire 4 upgrade guide, or wants to assess whether an app is ready for Livewire v4. Audit-first - establishes the lay of the land before any dependency changes.

Create a new GitHub repository from the current local project, push code, and handle finishing touches (README, LICENSE, description). Use when the user wants to publish a local project to GitHub for the first time. Triggers on: "github-create", "create a repo", "push this to github", "put this on github", "create a github repo", "let's make a repo", or any request to publish a local project to GitHub as a new repository.

Local-first issue tracker for coding agents. Use when planning work, tracking multi-step tasks, modelling dependencies, coordinating between agents, or resuming after session loss or conversation compaction. You must use this skill if the user mentions `ait`.

Structured process for technical recommendations and implementation advice. Use when the user asks for a recommendation, opinion, or approach ('what do you recommend', 'how should we', 'which option', 'what's your thinking'), or when you catch yourself about to volunteer an opinion on which option is best — especially with trade-offs or multiple valid approaches.

Users conventions and patterns for Go CLI/TUI projects. Use when working on a Go project

University of Glasgow Design System — use this skill whenever creating HTML, CSS, React, or any web UI that should follow the University of Glasgow brand. Triggers on: UofG, University of Glasgow, gla.ac.uk, Glasgow University web, or any request to build web pages/components using the Glasgow design system. Also use when the user asks for a Tailwind config, CSS variables, or design tokens for the University of Glasgow. This skill provides colours, typography, spacing, grid, and component patterns from the official UofG design system (design.gla.ac.uk).

Walk a developer through tidying up /opt/homebrew. Also use when hunting macOS disk space.

Defensive credibility check for deliverables (reports, dashboards, demos, presentations, web pages, marketing copy) aimed at a real human audience — especially when those readers have local context (a city, an institution, a profession) that lets them spot inaccurate or implausible details. Use this skill BEFORE generating the deliverable when it will mention specific places, buildings, organisations, distances, demographics, or named personas. ALSO use it as a final review pass on any visual or copy output before delivery, to catch design and copywriting tropes that have become recognisable "this came from an LLM" tells. Trigger reliably when the user mentions creating something for "my colleagues", "an audience", "a demo", "a presentation", "to share with stakeholders", or any output that needs to look credible and not AI-generated. Also trigger when the user names a specific institution, city, or audience their work is for. Especially important for demos meant to demonstrate AI capability — where one credi

Local-first notebook for *why* — design decisions, alternatives rejected, pivots taken, the conversational nuance that gets lost when an issue closes. Sibling to ait. Use when the user asks to record/note a decision, after a load-bearing choice between options, after a library swap or refactor of direction, or to recall prior decisions in an area.

Conventions for designing practical, consumer-friendly JSON APIs in Laravel with Sanctum. Use when adding or changing endpoints under routes/api.php or app/Http/Controllers/Api/, when reviewing an existing API for consistency, or when aligning multiple Laravel API apps on a shared shape. Optimised for non-developer consumers (Power BI, Excel, AI agents holding tokens) rather than strict OpenAPI compliance — the goal is "obvious from the response", not "minimal payload".

Convert a markdown plan (Claude plan-mode output, design doc, ait issue body, etc.) into a single self-contained, regular-user-friendly HTML file styled with the local design system. Use when the user wants to share a plan with non-technical stakeholders, send it for review, attach it to an email, or print it. Triggers on: 'turn this plan into html', 'export this plan', 'make this plan shareable', 'manager-friendly version', 'pretty version of this markdown', 'share this with my manager', or any request to convert a plan/spec/design markdown into a styled web document.

Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system.

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

Create Marp markdown presentations through a guided workflow. Asks about audience and source material, picks the right theme, and builds the slides. Self-contained — bundles three custom themes and handles project setup. Triggers on: presentation, slideshow, slides, Marp, deck, talk, or any request to turn notes/data into a presentation.

Create custom Marp presentation themes from a description or vibe. Asks about the aesthetic, audience, and feel, then generates production-ready theme CSS. Detects the i-impeccable skill for enhanced design guidance. Triggers on: marp theme, create a theme, presentation theme, slide theme, or any request to design a custom look for Marp presentations.

Flux UI v2 component reference for Laravel/Livewire. Use when building interfaces with Flux components - covers syntax, patterns, common mistakes, and modal/form/table patterns.

How we write Livewire components - principles, patterns, and testing. Use when building or reviewing Livewire components, tests, or Blade views.

Migrate older Laravel apps to modern Livewire + Flux UI. Source-framework mappings, checklists, and gotchas. References flux-ui and modern-livewire skills for target patterns.

Deploy and manage Laravel Cloud demo applications via the `cloud` CLI. Use when the user asks to deploy, create, update, or tear down a Laravel Cloud app. Triggers on keywords like "cloud deploy", "cloud ship", "teardown", "cloud teardown", "ship it", "push to cloud", or any reference to managing Laravel Cloud applications or environments.

Writes Standard operating procedure documents to a high technical standard. Use when the user asks for a 'sop' or standard operating procedure document

Generate a GitHub-style README.md for the current project by reading the actual codebase. Use when the user asks to "generate a readme", "write a readme", "document this project", "create a readme", or invokes /readme. Also callable from the github-create skill.

Convert a Claude Code or Codex CLI session into a beautiful, shareable single HTML file for presentations and workshops. Supports both Claude Code and OpenAI Codex CLI session logs. Use when the user wants to showcase, export, present, or share a coding agent conversation as HTML. Also triggers on: 'conversation to html', 'export session', 'share this conversation', 'make a transcript', 'session to html', 'presentation from session', 'showcase conversation', 'codex session', or any request to turn a Claude Code or Codex session into a shareable format. Should be used proactively when the user mentions workshops, demos, or sharing coding agent conversations.

Create a shell function or alias tailored to the user's current shell (bash, zsh, fish, etc). Generates portable, idiomatic code for the detected shell. Use when the user asks for a shell function, alias, helper, shortcut, or one-liner they want to keep. Triggers: 'shell function', 'alias', 'make me a command', 'add to my shell', 'bash function', 'zsh function', 'fish function', or any request to create a reusable shell command.

Propose CHANGELOG.md updates by analysing git tags and diffs. Uses Keep a Changelog format. Detects undocumented releases, reads actual code changes (not just commit messages), and outputs a proposed entry for review. Works with any language.

Set up and run PHPStan/Larastan static analysis on Laravel projects with sensible defaults that filter out Laravel magic noise. Iteratively fix real issues and progressively increase analysis levels. Use when the user asks to: run phpstan, run larastan, set up static analysis, check code quality with phpstan, add phpstan/larastan to a project, or "analyse my code". Also use when the user mentions phpstan.neon configuration.

Generate a TECHNICAL_OVERVIEW.md file for any codebase. Automatically detects the tech stack, explores models/routes/services, and produces a concise reference document that helps future AI sessions (or humans) quickly understand the project without re-exploring. Use when starting work on an existing project, onboarding to a new codebase, or creating documentation for your team. Works with Laravel, Rails, Django, Node/Express, and other common stacks.