Alastair Dawson
Community@kreek · Fullerton, CA
Alastair Dawson (kreek) publishes 24 engineering discipline skills covering software design, testing, security, databases, observability, and release management for full-lifecycle development.
Agent Skills by Alastair Dawson
Showing 24 vetted skills indexed across 1 GitHub repositories.
kreekui-design
Guides frontend UI design decisions covering layout, components, accessibility, and WCAG 2.2 AA compliance.
kreekdomain-modeling
Design domain data shapes, invariants, and state transitions with effects isolated at boundaries.
kreekcommit
Stage reviewed changes by name and write structured git commit messages.
kreekdatabase
Reviews database schemas, migrations, indexes, and query plans for locking and rollback risk.
kreekproof
Validates engineering claims with named tests, contracts, and runnable evidence.
kreekdocumentation
Write and maintain READMEs, runbooks, API docs, and code comments describing existing code.
kreekerror-handling
Design typed error contracts, propagation rules, and recovery behavior for software systems.
kreeksecurity
Review code changes for auth, secrets, input validation, and dependency risks.
kreekscaffolding
Scaffold new projects with approved toolchain, quality commands, CI, and smoke tests.
kreekgit-workflow
Manages git branches, history rewrites, conflict resolution, and force-push safety gates.
kreekcode-review
Review diffs and pull requests for bugs, security issues, and merge blockers.
kreekdebugging
Diagnose failures by reproducing symptoms and isolating root causes with evidence.
kreekrelease
Prepares version bumps, changelogs, and rollout plans for approved releases.
kreekobservability
Instrument services with structured logs, metrics, traces, alerts, and SLOs.
kreekcontract-first
Requires approval of caller-facing interfaces and shared structures before implementation begins.
kreekarchitecture
Guides module boundary, layering, and coupling decisions for software system organization.
kreekworkflow
Routes software engineering tasks by risk classification and selects skills for implementation and proof.
kreekapi
Designs and reviews REST API contracts covering endpoints, errors, pagination, and idempotency.
kreekrefactoring
Guides behavior-preserving code refactoring with proof contracts and incremental safe steps.
kreekofficial-source-check
Verifies version-sensitive framework and library behavior against official documentation sources.
kreekperformance
Diagnose bottlenecks and design caches using measurement-driven profiling workflows.
kreekasync-systems
Design and review async systems covering queues, streams, backpressure, and failure semantics.
kreekspecify
Guides collaborative design decisions before implementation through discovery, tradeoffs, and ADRs.
kreekship
Runs a gated maintainer flow for committing, merging, versioning, validating, and pushing releases.
Frequently Asked Questions About Alastair Dawson
FAQPage SchemaWhat tasks can I accomplish with kreek's skill collection?▼
The 24 skills cover the full engineering lifecycle: architecture decisions, domain modeling, contract-first endpoint design, database schemas and migrations, debugging, refactoring, code review, security hardening, performance profiling, async concurrency, accessibility-focused UI, documentation, and guarded release shipping.
Who is the target audience for these skills?▼
Software engineers, tech leads, and maintainers responsible for production systems. The skills suit practitioners handling design tradeoffs, PR reviews, incident response, schema evolution, and release validation rather than casual or beginner users.
How do the skills work together in practice?▼
The routing skill triages any feature, bug, refactor, or config task to assess risk and select relevant disciplines. Specify and contract-first skills lock decisions before building; proof, code-review, and commit skills validate and stage work; ship executes guarded merge, version bump, and push.
What prerequisites or dependencies do these skills require?▼
Skills assume an existing code repository with version control. Several reference concrete surfaces: git branches, rebases, and gh for history operations; CI and package setup for scaffolding; logs, metrics, and traces for observability; and REST endpoints for contract design.
Do these skills cover security and reliability concerns?▼
Yes. The security skill addresses auth, secrets, cryptography, trust boundaries, dependency risk, and untrusted input. Error-handling defines failure contracts, retries, and recovery, while observability covers health checks, dashboards, alerts, and SLOs for production reliability.