
Rules for structuring Vue 3 components so humans can read and maintain them
- Open source
- 28 GitHub stars

Rules for structuring Vue 3 components so humans can read and maintain them








Check planned AI coding actions and patches against explicit project constraints through SpecLock MCP tools

Check planned AI coding actions and patches against explicit project constraints with SpecLock

Detect, activate, or deactivate bundled knowledge patches.

Report bundled patch versions, activation state, age, and missing artifacts.

Route technology work to matching bundled knowledge patches.

Two-layer AI-tell audit of any text — deterministic scanner (lexicon, constructions, stylometry with line numbers) plus a blind semantic jud

One brief, N posts, N genuinely different people — voice-isolated writers, cross-post overlap detection, per-post verification receipts

Rewrite existing text so it reads human — either scrubbed-and-souled in its own register, or fully re-voiced as one of the roster's people


Build and maintain the user's OWN voice profile from continuously captured writing plus explicit samples — status, build/refresh, add sample

Create a new voice profile — from a writing corpus (measured, not vibed), or invented to fill a gap in the roster

Write a social post in one of the roster's voices (or the user's own `self` voice) — platform-native, craft-floored, scanner-verified

Service Workers and Progressive Web Apps

Service Workers and Progressive Web Apps

Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform, through t

Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the `ilo` CLI instead of on the host

LOG-UFPB's internal quick reference (group conventions, recommended tools, solvers and caveats from the group's own experience)

Use when items need categorical triage (critical/warning/ok), not numeric scoring

Use when you want to stress-test a proposal, plan, or findings before acting on them


Use when deciding between two approaches and you need a structured tradeoff comparison

Use when you want to browse available skills or find the right pipeline for a workflow