Coding & Development

Builds the information pack Apple asks for when App Review replies "We need additional information to better understand the app". It covers all six required items: (1) a screen recording on a physical device, as a shot list the user records; (2) the app's purpose and target audience; (3) setup and main features, with any login credentials or sample files; (4) the external services the app uses; (5) regional differences; (6) regulated industry or protected third-party material. It also runs Apple's "Prevent common issues" checks. Every answer comes from the app's own code (accounts, user-generated content, in-app purchases, SDKs, locales, screen-capture blocking, data deletion). It reads the connected iPhone's iOS version and checks it is the latest. It ends by telling the user to paste the reply into App Review Information → Notes. Use it when the user pastes that App Review message, says "/new-app-info", "we got rejected, they want more info", "answer App Review", or "make the App Store review pack". It w...

Develop inside an AINAS Coder workspace and ship the result as a NAS app: run commands in the isolated container, manage projects and project instances, trigger builds, and download or install the resulting .zpk. Use when the user asks to build, test, package, or install a project through Coder.

Expert drafting and review of Delaware C-corporation startup legal documents from formation through Series A: certificate of incorporation, bylaws, incorporator and board consents, founder stock purchase agreements, IP assignments, 83(b) elections, equity incentive plans and option/RSU/RSA grants, offer letters, CIIAAs, consulting/advisor/separation agreements, NDAs, SAFEs and side letters, convertible notes, term sheets, NVCA-style priced-round documents, board and stockholder consents, Section 204 ratifications, charter amendments, and compliance (franchise tax, foreign qualification, Form D and blue sky, 409A, Rule 701, ISOs, QSBS). Use when someone forms or runs a Delaware corporation, issues equity, hires, raises money, or asks to draft, fill in, review, or explain any of these documents or deadlines.

Builds, configures and debugs Socket.IO 4.8 servers and clients from the official Socket.IO v4 documentation. Use when writing a Node.js Socket.IO server (Express, Fastify, Koa, Bun, uWebSockets.js) or a socket.io-client app, emitting events with acknowledgements, timeout() and emitWithAck, broadcasting to rooms and namespaces, authenticating in middleware with the auth option, configuring CORS, reverse proxies and sticky sessions, scaling with the Redis, Redis Streams, Postgres, MongoDB or Cluster adapter, enabling connection state recovery and delivery guarantees, tuning reconnection, writing tests, troubleshooting connection issues, or migrating from Socket.IO v2 or v3. Triggers on Socket.IO, socket.io, socket.io-client, io(), new Server, emit, emitWithAck, acknowledgements, rooms, namespaces, broadcast, io.use, middleware, CORS, Redis adapter, sticky sessions, connection state recovery, reconnection, connect_error, Session ID unknown. Not for plain WebSocket servers such as ws without Socket.IO.

Runs desk research and writes a technical guide to .knowledge/{domain}/{topic}/guide.md in the open project. Reads at least five high-relevance primary sources, records the tool that found each source, and draws the macro and micro process. Use when the user says /learn, asks for a study guide or desk research, or gives a subject or link to study.

Runs a cEDH (competitive Commander) playgroup on top of TopDeck.gg tournament data. Use it to add players and their decks, pull each player's tournament results from TopDeck.gg, report the recent meta (last month by default), log practice games, notes and who can make a session, and build practice pods that face the top meta, stay balanced, avoid repeat pairings and target each player's weak matchups, and post pods, meta reports, results and "who's in?" calls to the group's Discord channel. Use it whenever the user mentions their playgroup, pod or practice night, testing partners, TopDeck stats for people they play with, "what's the meta right now", a practice game result to record, seating people for cEDH, or posting any of that to Discord, even if they don't say "skill" or "TopDeck".

Run a grilling interview on a local browser page instead of the terminal. Every question is laid out with its recommendation, answerable in any order, with a per-question discussion thread and one "Send to Agent" button. Use when the user says "grill with ui", invokes /grill-with-ui with a topic, or says "/grill-with-ui resume".

Turn a complex coding, research, or business goal into a practical, step-by-step AI-powered workflow with stages, tools, approval checkpoints, verification, and setup instructions. Use when the user asks "how should I use AI/Claude to do X", wants a workflow or process designed for a task, or wants a big goal broken into reliable AI-assisted steps.

Independent review stage of Full-Stack WP Developer. Reviews a finished WordPress plugin, theme, add-on, or Core patch through a security lens (WordPress-specific vulnerabilities, REST and AJAX authorization with an API risk map, AI-generated-code risks), a quality lens (error handling, data and upgrade safety, performance, i18n, accessibility, comment accuracy, test gaps, class and type design, scope), and an optional lean lens for trimming over-engineering, reporting only high-confidence findings in a fixed format. Invoked by fswp-developer after the verify gate, normally through the fswp-code-reviewer agent; consult directly to review or optimize any WordPress code.

Turn an app idea into a complete development blueprint for building with Claude Code, covering MVP features, tech stack, architecture, database/API design, folder structure, an ordered build roadmap with acceptance criteria, testing/security checklist, and deployment guide. Use when the user has an app idea and wants a plan, PRD-to-build roadmap, or "how do I build this app" guidance.

Design and review product screens around real user tasks, information priority, and state transitions. Use for new or changed UI flows and cluttered interfaces; skip UI design for non-UI tasks.

Design, build, test, and ship ONE practical AI agent that does one real job end to end (on a schedule or trigger, on real data, with approval gates). Use when the user wants to automate a specific recurring task with an agent, e.g. "build me an agent that every morning finds X and drafts Y". Supports any runtime, including Claude Code, scripts, or Grok Bot.

Système de marque sobre et éditorial, fourni comme marque par défaut : palette bleue sur fond clair, typographie Inter, dégradé doux, boutons en pilule, cartes à ombre légère, icônes Phosphor. Appliquer à tout livrable (présentation, document, page, artefact web) quand aucune autre charte n'est donnée, ou s'en servir comme modèle à remplacer par la charte d'un projet. À combiner avec `slides` (mises en page) et `pptx` (génération du fichier). Déclencher dès qu'on demande une mise en forme soignée, une identité visuelle, des tokens de design, ou un livrable client à l'aspect professionnel.

Planning heating, hot-water and solar control systems with Technische Alternative (TA) products – for homeowners planning their own system and for installers. Use when someone wants to choose a TA controller (UVR16x2, UVR610, UVR67, CAN-I/O45, CAN-EZ3, CAN-BC2, CAN-MTx2, C.M.I.), count inputs and outputs, pick sensors, immersion sleeves, flow sensors, room sensors or auxiliary relays, design the CAN or DL bus, write a bill of materials with article numbers and list prices, find the right datasheet or manual on ta.co.at, pick a program from the TA program library, or check which Austrian standards, OIB guidelines, state law and funding conditions apply. Also use for German requests like "welchen Regler brauche ich", "Stückliste UVR", "Fühler planen", "Heizungsregelung planen", "Kesseltausch Förderung Regelung". For operating or analysing an existing TA installation use the skill technische-alternative instead.

A borehole logging engineer's knowledge: field logging at the rig, soil and rock description systems (USCS/ASTM, Canadian, AS 1726, BS 5930), sampling and in-situ tests (SPT, pocket penetrometer, torvane, vane, DCPT, CPT), rock core logging (TCR, RQD, weathering, fractures), groundwater, wells, the field-log to final-log transformation, and what a reviewer checks before sign-off. Use it whenever work needs that judgement: designing or reviewing a GroundScribe logging feature, QA rule, extraction prompt, export template or fixture; interpreting a field-sheet value; checking a log; onboarding a new firm's conventions; or judging the product as a logger would. Trigger even without the word "logging", e.g. "is N=6 dense sand ok", "what does 50/5 mean", "how should we store torvane", "S.A.A.", "RQD", "EOH".

Make a single-image editorial infographic (1080x1350) that explains one idea at a glance — two-tone headline, one-sentence dek, a hero visual with 2–4 numbered callouts and leader lines, an optional side note, a three-column "why it matters" row with icons, byline and sources. Use for "explain X in one graphic" posts about a company move, a framework, an architecture or a trend; the PNG can also be a carousel slide.

Build or refresh a shortform brand reference pack for any app from its real surfaces — website, App Store listing and reviews, socials, the live app (driven end to end on the simulator) and its code tokens — plus a status check of the upstream foundations (ICP, voice of customer, brand voice). Produces the context that content formats and design decisions are made from, as markdown, tokens.json and a PDF. Use for "build a brand pack for <app>", "refresh the brand pack", "capture the site/app/socials for shortform", "/brand-reference-pack".

Use only when the user asks to design a mobile UI screen or flow (phone-sized layouts, touch targets, thumb reach). Do not use for tablet, desktop, or non-UI work.

Grafana Cloud pitfalls, defaults, limits and current patterns from the Grafana, Mimir, Loki and Tempo docs, each tied to its docs URL. Use when sending OpenTelemetry data to Grafana Cloud, writing PromQL, LogQL or TraceQL, controlling cardinality and cost, designing alert rules, routing notifications, provisioning alerting, building Synthetic Monitoring checks, using the /apis dashboard API, choosing access policy tokens or service accounts, or migrating off API keys, the Loki Exporter and legacy /api routes.

Design technically accurate telecom architecture infographics, interactive HTML explorers, animated signaling flows and architecture comparisons. Use this skill whenever the user wants to visualize, illustrate, diagram, explain or compare any telecom topic (2G/3G/4G/5G, IMS, VoLTE, roaming, S8HR vs LBO, IPX, Diameter, SIP, GTP, SS7/MAP, SMS routing, CAMARA / GSMA Open Gateway APIs, SIM Swap, Number Verification) as an infographic, interactive architecture explorer or animated signaling flow, even if they never say "infographic" or "skill". For LinkedIn packaging of the result, hand off to telecom-linkedin-publisher.

Pitfalls, surprising defaults, PostgreSQL 18 changes and recommended patterns from the official PostgreSQL 18 documentation, each backed by its postgresql.org URL. Use when writing or reviewing PostgreSQL SQL, schema design, migrations and ALTER TABLE locks, indexes, transactions, isolation levels and retries, locking, upsert and MERGE, COPY, JSONB, timestamptz, generated and identity columns, partitioning, EXPLAIN, vacuum, roles, row-level security, PL/pgSQL, full-text search, connection settings, and upgrades to PostgreSQL 18.

Use only when the user asks for a UX review or critique of an existing UI design, screen, or flow. Do not use for code review or non-UI work.

Pitfalls, surprising defaults and recommended patterns of the Typesense search engine, distilled from the official docs. Use when designing a Typesense collection schema, writing search parameters (q, query_by, filter_by, sort_by, facet_by, group_by), tuning typo tolerance and ranking, building vector, semantic or hybrid search, conversational RAG or natural language search, creating API keys and scoped search keys for multi-tenancy, indexing and import (JSONL, upsert, emplace, dirty_values), syncing from a primary database, reindexing through aliases, managing synonyms (synonym sets), curation sets and stopwords, joins, analytics rules and query suggestions, InstantSearch, migrating from Algolia, or running, clustering, backing up and upgrading a Typesense server.

Use only when the user asks to design a desktop UI screen or flow (resizable windows, min/max sizes, pointer and keyboard). Do not use for mobile, tablet, or non-UI work.