version-bump
Bump version across all looplia-core package.json files, changelog, and documentation. Use when: releasing a new version, preparing a version bump PR, updating version numbers across the monorepo. Handles all 5 package.json files, CHANGELOG.md, docs/README.md, and the landing page version badge.
pptx-design
PowerPoint/PPTX design for Dome. Use when creating ppt_create with script (Python/python-pptx) or spec. Palettes, typography, layouts. Script must call prs.save(os.environ['PPTX_OUTPUT_PATH']).
goreleaser-releasing
Set up GoReleaser for Go CLI/binary projects. Use when introducing binary releases, goreleaser config, release workflows, or Taskfile release tasks.
yamljsontoml-converter
Convert between YAML, JSON, and TOML configuration formats
update-dependencies
Update pinned dependency versions in this repository. Use when Codex needs to bump Docker base-image digests, lint/test container images, Kubernetes image tags, GitHub Actions workflow pins, or Maven dependency and tooling versions in `docker/sample-build.env`, `docker/*/Dockerfile`, `docker/build-*.sh`, `kubernetes/kustomization.yaml`, `test/kubernetes/*.yaml`, `test/*.sh`, `.github/workflows/ci.yaml`, or `console/pom.xml`. Prefer the latest upstream LTS release when the dependency publishes one; otherwise prefer the latest upstream release that stays on the current OS or image variant unless the user asks to change tracks.
migrate-legacy-implementation
Migrate a legacy source connector from the old sources/ directory to the new package structure under src/databricks/labs/community_connector/sources/.
build-connector-package
Create a pyproject.toml for a source connector and build it as an independent Python package.
project-structure
Navigate the nix-config repository layout and find files
frontend-web-engineer
Expert frontend web development including HTML/CSS/JavaScript implementation, responsive design, accessibility improvements, and Playwright browser automation testing. Balances modern frameworks with pragmatic vanilla solutions. Use when working with web frontends.
chatgpt-app
Guidance for building the chatgpt-app (Vite + React + @openai/apps-sdk-ui) with the MCP-friendly single-file output.
add-domain-entity
Create domain layer components: models, repository interfaces, marshallers, and implementations. Use when: (1) adding domain model in internal/domain/model/, (2) creating repository interface in internal/domain/repository/, (3) implementing repository with marshaller in internal/infrastructure/{db}/. This is Step 2 of CRUD workflow (after add-database-table, before add-api-endpoint).
error-handling
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
operating-production-services
SRE patterns for production service reliability: SLOs, error budgets, postmortems, and incident response. Use when defining reliability targets, writing postmortems, implementing SLO alerting, or establishing on-call practices. NOT for initial service development (use scaffolding skills instead).
software-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
frontend-design
Premium/yaratıcı UI tasarım. ⚠️ Distinctive, memorable interface için kullan. Temel UI için → design-patterns.
microservices-architect
Distributed systems architect specializing in microservices design patterns. Invoke for service boundaries, domain-driven design, saga patterns, event sourcing, service mesh, distributed tracing. Keywords: microservices, service mesh, distributed systems, Kubernetes, event-driven.
arch-patterns
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
state-management
State persistence patterns for autonomous-dev including JSON persistence, atomic writes, file locking, crash recovery, and state versioning. Use when implementing stateful libraries or features requiring persistent state.