← all publishers

zeybek

@zeybek source repo

4 published skills

  1. Apex Design · zeybek bundle
    Use this skill when turning a software change or new initiative into an implementable, reviewable plan before building — including a short or one-line request (such as a feature or page asked for in a single sentence) that should be scoped through clarifying questions first. Apply it to feature planning, architecture decisions, technical designs, API or schema evolution, data migrations, service boundaries, build-versus-buy choices, and reliability planning that need explicit requirements, alternatives, risks, contracts, and a sequenced task plan. It can be invoked directly or as a command, and it produces a persistent planning workspace that the implementation, review, and investigation workflows consume. Do not use it when a change is already decided and only needs implementation.
    0
    installs
  2. Apex Review · zeybek bundle
    Use this skill when asked to review code, a diff, pull request, patch, migration, design implementation, or repository change. Perform a language- and framework-independent, risk-first review for correctness, security, data integrity, concurrency, compatibility, reliability, maintainability, performance, and missing verification. Report actionable findings by severity and location; do not use it to implement fixes unless explicitly requested.
    0
    installs
  3. Apex Implement · zeybek bundle
    Use this skill when implementing software changes end to end with language- and framework-independent senior engineering judgment. Apply it to features, bug fixes, refactors, debugging, integrations, migrations, configuration, dependencies, executing a planned `.apex-design/<slug>/` workspace, and production-facing code work that requires inspecting the existing system, controlling risk, preserving contracts, and verifying results. Do not use it for review-only or design-only requests.
    0
    installs
  4. Apex Investigate · zeybek bundle
    Use this skill when investigating a failure whose cause is not yet known — a production incident or outage, a regression, an intermittent or flaky failure, a performance degradation, corrupted or surprising data, or a bug report you must diagnose before fixing. Apply it to triage severity and mitigation, gather and preserve evidence, form and test hypotheses, bisect and localize the cause across components and time, read logs, metrics, and traces, confirm a root cause by mechanism, and record findings in a blameless writeup. Do not use it when the change is already understood and only needs implementation (use apex-implement) or when reviewing a proposed change (use apex-review).
    0
    installs