llblab
- 12 skills
- 0 followers
- 1 week ago last updated
- ▌ Release Flow · llblabSelect and run a guarded GitHub release flow for an administered repository, using a pre-PR squashed dedicated version branch, a dev-to-main pull request, or direct main as repository topology requires, then coordinating tags, GitHub Releases, and optional existing npm publication. Use only with explicit release intent and ADMIN permission; exclude contribution forks, ordinary feature integration, and non-GitHub workflows.
- ▌ Coding Contract · llblabDefault senior-engineer execution and safety contract for software engineering work, including implementation, debugging, refactoring, tests, code review, review remediation, configuration, builds, CI, schemas, migrations, validation, repository maintenance, file edits, and technical investigation. Use whenever software work needs scoped autonomous execution. Resolves authority, binds the active contract, admits only necessary acts, validates the retained state, and stops at an evidenced local fixed point while leaving domain-specific judgment to specialized skills.
- ▌ Frontend Design · llblabDesign, implement, refactor, or review user-facing interfaces. Use whenever work changes how a web or app surface looks, reads, responds, or is operated, including components, pages, forms, dashboards, responsive behavior, accessibility, visual polish, and design systems.
- ▌ Show Me · llblabExplain the current topic or work through contextual Markdown replies, concise diagrams, code-shape sketches, and focused HTML artifacts.
- ▌
- ▌
- ▌ Re Review · llblabEvidence-grounded review for code, diffs, PRs, documents, plans, specs, and architecture. Use for evidence review, review, code review, quick review, sanity check, quality check, architecture review, production readiness, security review, scaling review, document review, over-engineering review, simplification review, what can be deleted, bloat, evaluate, or check.
- ▌ Domain Dag · llblab bundleValidates and guides Domain DAG architecture for domain ownership, acyclic local dependency graphs, composition roots, boundary direction, public contracts, interface-surface pressure, and shared-bucket drift. Use when auditing, refactoring, or extending modular codebases across frontend, backend, extensions, CLIs, SDKs, and service packages.
- ▌ Extra Self · llblabHigh-density systems and memetic reasoning mode. Use for strategic synthesis, first-principles framing, deep structure, architecture-first analysis, product/platform/protocol/governance/economics design, institutional or incentive diagnosis, naming and category design, narrative or ideological analysis, capture and phase-change mapping, competing hypotheses, prompt/spec compression, or explicit cues such as extra self, be yourself, give me the base, dense version, deepest structure, or memetic read.
- ▌ Brain Storm · llblab bundleCollaborative idea-to-design and inquiry protocol. Use for product/architecture exploration, research-style question shaping, feature design, standards, specs, UX concepts, module boundaries, and non-trivial behavior changes when uncertainty matters.
- ▌
- ▌ Abcd Context · llblab bundleABCd context protocol across ABC root files (AGENTS.md, BACKLOG.md, CHANGELOG.md), human entrypoint README.md files tree, and /docs. Use after meaningful project changes, backlog drift, documentation refactors, self-evolving context maintenance, or a forced context reconciliation pass.