TechSpokes

Use when working in a consumer project that depends on @techspokes/typescript-wsdl-client to generate typed SOAP clients, OpenAPI specs, Fastify gateways, apps, tests, or catalogs from WSDL or catalog inputs.

Build a real agent skill from user-provided intake material. Use this placeholder only while the repository is still in bootstrap mode and before an agent has generated the final skill package.

Use when Codex is working in a project opened in PhpStorm and should decide how to use PhpStorm MCP tools for project configuration, search, inspections, quick fixes, formatting, symbol refactoring, execution, HTTP Client request files, Composer or PHP checks when present, database probes, IDE action discovery, or validation. Use to route between IDE-owned semantic context and terminal tools while avoiding unsafe or low-observability IDE actions.

Use when building, reviewing, debugging, or changing self-hosted Directus backends in SaaS repositories, especially behind an API proxy, gateway, or reverse proxy. The skill makes the agent inspect the repository architecture and versions first, research current official Directus and detected-stack docs, then plan, implement, and verify schema, environment, extension, auth, permissions, deployment, API, proxy, migration, security, observability, or AI/MCP changes without imposing a fixed reference stack.

Coordinate GitHub repositories across personal accounts and organizations while preserving goals, authority, privacy, workspace roles, and existing workflows. Use for access diagnosis, inventory, findability, portfolio understanding, repository routing, cross-repository work, practice reuse, functionality and knowledge reuse, tool comparison, initial orientation, installation and updates of this skill, or an explicit language quality review of coordination output generated by this skill. Supports software, documentation, writing, research, data, operations, and mixed work. Do not use as the primary workflow for routine work in one known repository or blanket destructive execution inferred only from inactivity; require lifecycle evidence.

Teaches an AI agent to build a database introspection capability inside the repository it is working in. Introspection is a read-only tool that reads a live database's catalogs and renders the current structure, security (row-level security, roles, grants), views, functions, and extensions into committed, navigable files shareable without a running database or credentials. Use when a repository needs an always-current, addressable picture of its database state, when asked to introspect a database, generate or refresh database state, make a schema readable for humans and agents, audit which callers can reach which objects, or capture the architect's intent behind the schema. The method is database-agnostic with a PostgreSQL reference implementation, and extends to layers around the database such as the cluster, a connection pooler (PgBouncer), and a REST layer (PostgREST). Not for authoring migrations, asserting expectations (that is validation), or writing hand-maintained documentation.