ZBSS
Official@zb-ss · United Kingdom
Standardizes enterprise software development through rigorous coding conventions, quality gate enforcement, and structured implementation procedures for web application lifecycles.
Agent Skills by ZBSS
Showing 32 vetted skills indexed across 2 GitHub repositories.
zb-ssWorkflow Learn
Extract reusable patterns from workflow sessions and save them to CLAUDE.md or skill files.
zb-ssmode
Switch workflow execution mode and update org-mode and JSON state.
zb-ssverify
Run build, type, lint, test, security, and diff checks across a project.
zb-sstest-live
Run interactive Playwright MCP browser tests against a live web application.
zb-ssResume Workflow
Resume interrupted Claude workflows from saved plan state files.
zb-sssetup
Configure Claude Code permissions and initialize workflow directories.
zb-ssWorkflow Orchestrator
Coordinates automated end-to-end Dev workflows for Claude Code with tiered agents and repo-scoped persistence.
zb-ssWorkflow Status
Retrieves Workflow state from .org/.md files in plugin and legacy directories.
zb-ssSkill Create from Git History
Generate project-specific SKILL.md files from git commit history.
zb-sssetup-statusline
Configure a terminal status line in Claude settings for API usage and cost.
zb-sstest-e2e
Generate Playwright end-to-end test suites from an app map.
zb-ssEpic Orchestration Instructions
Orchestrate multi-component software workflows with isolated git worktrees and dependency-ordered merging.
zb-ssPlanning phase procedures - plan output format, architecture analysis, risk identification
Generate an end-to-end implementation plan with architecture analysis, file changes, steps, testing, and risks.
zb-sscompletion guard procedures
Re-run tests and builds to verify requirements, quality, and state before approval.
zb-ssQuality gate procedures - build/type/lint/test pipeline, auto-fix loop, changes signaling
Run build, type-check, lint, test, and security pipeline with auto-fix loop.
zb-ssCommon Phase Instructions
Standardize workflow phase agent file operations and state tracking.
zb-ssReview phase procedures - verdict rules, issue format, re-review protocol, zero-tolerance policy
Enforce zero-tolerance PASS/FAIL verdicts with structured ISSUE reporting on changed files.
zb-ssImplementation phase procedures - fix protocol, code writing rules, review issue handling
Implement workflow plans while resolving numbered review issues with fix-by-ID reports.
zb-sspost-merge-review
Validate merged changes against original scope with parallel functional, security, and quality reviews.
zb-ssperformance-guide
Optimize web application performance across PHP, JavaScript, and database layers.
zb-sssymfony-conventions
Enforce Symfony best practices for services, Doctrine ORM, Twig, forms, and dependency injection.
zb-sssolid-principles
Explain SOLID principles with PHP and TypeScript code examples.
zb-ssapi-design
Designs RESTful APIs with PHP/Laravel implementation examples.
zb-sslaravel-conventions
Enforce Laravel 10+ conventions for Eloquent, controllers, validation, and testing.
Frequently Asked Questions About ZBSS
FAQPage SchemaWhat specific development tasks are enabled by these standards?▼
These standards enable systematic enforcement of coding conventions for PHP, Laravel, Symfony, and TypeScript. They provide structured procedures for architecture analysis, risk identification, and the execution of quality gates including build, type-checking, linting, and security verification.
Which engineering personas benefit from these implementation procedures?▼
Full-stack developers, software architects, and quality assurance engineers benefit from these procedures. They are designed for teams maintaining complex web applications who require consistent code quality, standardized testing protocols, and rigorous review cycles to minimize technical debt.
What are the prerequisites for integrating these quality gate procedures?▼
Integration requires a project environment configured for modern PHP or TypeScript development with existing support for Playwright testing. Users must initialize the repository with the provided configuration files to enable state tracking and the structured implementation fix-by-ID protocol.