Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## Unreleased

- Accept the reviewed Skills update from `472c216f2f043f0add1f83540cc46ea53d20a7cd` to `352eaf7b167a6761161415711ef9d55db26d91d6` as `0.1.0-canary.7` through a separate protected PR, because the range changes sensitive paths. Includes the published `@vllnt/*` package defaults annex and new direct improvement, session-refocusing, and full-environment PR testing workflows. The automatic sensitivity policy is unchanged.

- Add a `Privacy Guard` workflow: gitleaks over full history plus a structural denylist check with an allowlist, optional private patterns, and withheld match content.

## 0.1.0-canary.6
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.1.0-canary.6
0.1.0-canary.7
2 changes: 1 addition & 1 deletion plugins/claude/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,5 +14,5 @@
"license": "MIT",
"name": "vstack",
"repository": "https://github.com/vllnt/stack",
"version": "0.1.0-canary.6"
"version": "0.1.0-canary.7"
}
130 changes: 88 additions & 42 deletions plugins/claude/SOURCE.json

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,14 @@

- The contract identifies the candidate, mode, applicable rules, criteria, evidence, and perspective coverage before evaluation.
- Self-assessment, review, critique, and finding dispositions are traceable.
- Authorized code changes have a current pre-commit reduction check: task-owned additions are justified or simplified, with preserved contracts and renewed affected proof.
- `PASS` has current proof and scoped acceptance; missing independence or proof remains explicit.
- Authorized revisions receive renewed affected checks and verdicts.

## Procedure

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. In authorized code-change mode, require a reduction pass before each commit or final uncommitted handoff: compare the complete task delta with its verified baseline, including earlier task commits, staged, unstaged, and new files. Challenge additions with deletion, reuse, consolidation, or a narrower change at the existing owner. Have the caller apply supported reductions, not merely recommend them; justify retained complexity against the current contract and maintainability. Preserve required features, compatibility, security, failure handling, meaningful test detection, and unrelated or mixed-owner edits. Uncertain attribution or necessity is a gap, not permission to delete. Fewer lines alone, minification, hidden work, and deletion quotas are not success. Rerun invalidated checks and renew affected review after reductions; reuse current proof rather than repeat unchanged passes. Read-only work assesses or proposes, never performs code cleanup. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

## Procedure

1. Define consumers, component-owned state/lifecycle, host-owned identity/domain data, public operations, failures, retention, pagination, tenant scope, and installed API assumptions. Reuse an official component when it fits.
1. Define consumers, component-owned state/lifecycle, host-owned identity/domain data, public operations, failures, retention, pagination, tenant scope, and installed API assumptions. Reuse an official component when it fits; for Vstack projects, start with the matching `@vllnt/convex-*` component and `@vllnt/convex-helpers` from [default packages](../project-alignment/references/default-packages.md).
2. Keep schema, functions, generated files, and schedules inside the component boundary. Host and siblings use generated references and `ctx.runQuery`, `ctx.runMutation`, or `ctx.runAction`; never hand-edit generated files.
3. Validate exported arguments and returns at runtime. Keep queries read-only, mutations transactional, and external effects in actions; bound batches and make retries and partial external failure recoverable.
4. Require the host to authenticate, derive trusted scope, and authorize before calls. Keep host secrets, schemas, and privileged wrappers outside the component.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

## Procedure

1. Set the consumer config, shared preset, or custom rule. Sample source, tests, configs, generated files, and framework files; inspect effective configuration with the installed CLI when available.
1. Set the consumer config, shared preset, or custom rule. When a Vstack project has no shared preset, default to `@vllnt/eslint-config` 2.x per [default packages](../project-alignment/references/default-packages.md). Sample source, tests, configs, generated files, and framework files; inspect effective configuration with the installed CLI when available.
2. Use installed flat-config forms and deliberate order. Scope rules, globals, parsers, environments, and ignores precisely; keep ordinary source outside generated-file exclusions.
3. Enable typed linting only for files in the correct TypeScript project. Preserve public preset names, severity, peer dependencies, and formatter behavior; narrowly justify exceptions.
4. For shared presets, test an isolated packed consumer. For custom rules, test valid/invalid forms, rule IDs, false positives, and safe autofix followed by a second lint pass.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
1. Map requested surfaces, existing behavior, entry points, manifests, lockfiles, runtime versions, integrations, authentication, data owners, and current checks. Mark missing evidence.
2. Resolve the target from applicable instructions. Distinguish existing configuration from the desired state. Select the smallest reversible option supported by evidence; for consequential conflict, state options, recommendation, impact, and the required decision while continuing unaffected analysis.
3. Use [Stack packages](../stack-packages/REFERENCE.md) for current source, registry, and consumer evidence when available. Otherwise gather equivalent scoped evidence: selected manifests, paginated source or registry results, exact latest or canary metadata, and consumer declarations or lock resolutions.
4. Match each needed function to a preferred existing package before proposing custom code or another dependency. Verify exact published version, permitted channel, exports, peers, engines, runtime, maintenance or license fit, and required setup.
4. Match each needed function to a preferred existing package, starting with the [default packages](references/default-packages.md), before proposing custom code or another dependency. Verify exact published version, permitted channel, exports, peers, engines, runtime, maintenance or license fit, and required setup.
5. Return a decision for each candidate: use, keep, replace in a named stage, or exclude with evidence. Check cross-surface constraints and extension points; maximize useful reuse rather than package count.
6. Define canonical data and authorization owners, client or server boundaries, permitted caches, and external interfaces from target rules. Identify duplicate durable state and business rules.
7. Produce small dependency-ordered stages with consumers, behavioral acceptance checks, and recovery. For existing data changes, include mapping, identity or access preservation, validation, cutover ownership, and rollback or roll-forward criteria.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
# Default @vllnt packages

Preferred foundations for Vstack projects, from the [@vllnt npm scope](https://www.npmjs.com/org/vllnt). For a listed function, use its package before custom code or a third-party alternative. Keep an existing equivalent only when consumer rules or a contract in use require it, and record that exception.

## Channel rules

- Stable packages: default to the latest stable release.
- Canary-only packages: pin the exact version listed here until a stable release exists. Moving the pin is a deliberate change with its own verification.
- `@vllnt/typescript` and `@vllnt/eslint-config`: default to the 2.x line.
- Before relying on an entry, confirm it is still published, not deprecated, and compatible with the consumer's framework, TypeScript, and runtime peers.
- For a function not listed, use the Stack packages procedure when installed; otherwise query the registry scope directly. Do not name, assume, or create a package; report the gap as a package request.

## Tooling and UI

| Function | Package | Channel |
|---|---|---|
| TypeScript configuration | `@vllnt/typescript` | stable, 2.x |
| ESLint configuration | `@vllnt/eslint-config` | stable, 2.x |
| Web UI components | `@vllnt/ui` | stable |
| Shared and native UI primitives | `@vllnt/ui-core`, `@vllnt/ui-native` | canary-only, pin `0.1.0-canary.20260917105553.sha7466647a4ba5` |
| Structured logging | `@vllnt/logger` | stable |
| Client analytics with consent | `@vllnt/analytics` | stable |
| `llms.txt`, `llms-full.txt`, and raw-markdown pages for Next.js | `@vllnt/next-llms` | canary-only, pin `0.1.0-canary.bca5ab7` |

`@vllnt/ui-native` is for Expo and React Native; do not infer mobile support for `@vllnt/ui` or `@vllnt/analytics` from React compatibility.

## Convex

Use `@vllnt/convex-helpers` for host-side builders, errors, validators, pagination, HTTP, env, and observability. Mount a component below only when the product needs its function; membership in this table does not make every component relevant.

| Function | Package | Channel |
|---|---|---|
| Host helpers | `@vllnt/convex-helpers` | stable |
| Event ledger and activity feed | `@vllnt/convex-events` | stable |
| Analytics rollups, funnels, retention | `@vllnt/convex-analytics` | stable |
| Consent ledger | `@vllnt/convex-consent` | stable |
| Do-not-contact list and opt-in proof | `@vllnt/convex-suppression` | stable |
| Roles and grants | `@vllnt/convex-permissions` | stable |
| Membership and relationship graph | `@vllnt/convex-memberships` | stable |
| Invitations | `@vllnt/convex-invitations` | stable |
| Hashed-secret tokens | `@vllnt/convex-tokens` | stable |
| Feature flags | `@vllnt/convex-flags` | stable |
| A/B experiments | `@vllnt/convex-experiments` | stable |
| Idempotency keys | `@vllnt/convex-idempotency` | stable |
| Usage metering | `@vllnt/convex-metering` | stable |
| Consumable balances and spend ledger | `@vllnt/convex-wallet` | stable |
| Transactional email queue | `@vllnt/convex-email` | stable |
| Notifications inbox | `@vllnt/convex-notifications` | stable |
| Comments and annotations | `@vllnt/convex-comments` | stable |
| Reactions, votes, likes | `@vllnt/convex-reactions` | stable |
| Unique slugs and handles | `@vllnt/convex-slugs` | stable |
| Provider-neutral music catalog | `@vllnt/convex-music` | stable |
| Ephemeral subject groups | `@vllnt/convex-buckets` | canary-only, pin `0.1.0-canary.0` |
| XP, levels, streaks | `@vllnt/convex-progression` | canary-only, pin `0.1.0-canary.0` |
| Scheduled per-subject allowances | `@vllnt/convex-quota` | canary-only, pin `0.1.0-canary.0` |

## Other

`@vllnt/dig` (canary-only, pin `0.1.0-canary.fcb1735`) is a TypeScript client for a local knowledge-base daemon. Use it only when a project already runs that daemon.
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
- Published package has no accessible source: retain it with registry evidence and a source gap.
- Repository has a package manifest but registry returns 404: do not list it as published.
- Latest points to a prerelease; canary is missing or older: preserve exact facts and explain the selected channel/fallback.
- Canary is older but compatible and no freshness policy exists: report its date/version order, retain the preferred testing channel, and do not invent a staleness threshold.
- Canary is older but compatible and no freshness policy exists: report its date/version order, keep the consumer's selected channel (an exact canary pin stays pinned), and do not invent a staleness threshold.
- Shared configs require incompatible TypeScript peers: return the incompatible set and a compatible alternative or unresolved decision.
- Consumer uses a canary range but its lockfile resolves another version: report both; do not claim the tag is installed.
- Private package is denied or a recursive tree is truncated: return partial coverage rather than an empty or complete inventory.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
1. Inspect consumer instructions, scripts, lockfile, tsconfig inheritance, exports, compiler binaries, and fixtures. Record supported compiler, runtime, framework or bundler versions, module format, and emission owner.
2. Capture every affected effective configuration with the installed compiler's `--showConfig`. Resolve inheritance before editing a shared base; inspect compiler-API consumers such as linters or build plugins separately from CLI compilation.
3. Select settings by consumer: Node needs compatible module, resolution, and extensions; libraries need matching emitted JavaScript, declarations, and exports; bundled apps need supported JSX or resolution; framework-owned builds retain their required plugins and generated includes without competing emit.
4. Keep bases small. Make consumers own layout-specific roots, outputs, includes, and ambient types. Treat strictness, target, lib, types, paths, inherited relative paths, and array replacement as explicit contracts.
4. Keep bases small. When a Vstack project has no shared base, default to `@vllnt/typescript` 2.x per [default packages](../project-alignment/references/default-packages.md); verify its exports and peers first. Make consumers own layout-specific roots, outputs, includes, and ambient types. Treat strictness, target, lib, types, paths, inherited relative paths, and array replacement as explicit contracts.
5. Identify the cause before using `skipLibCheck`, weaker strictness, or a compiler upgrade. State its tradeoff.
6. Verify changed presets with positive and negative diagnostic fixtures, representative resolution, and emit behavior. Inspect emitted JavaScript, declarations, and maps; execute relevant output or prove no artifacts for no-emit configurations.
7. For published presets, compile an isolated consumer installed from the packed package without workspace-only dependencies. Run affected framework or bundler builds, including generated types and JSX. For a fix, show isolated failure then success and rerun invalidated checks.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,14 @@

- The contract identifies the candidate, mode, applicable rules, criteria, evidence, and perspective coverage before evaluation.
- Self-assessment, review, critique, and finding dispositions are traceable.
- Authorized code changes have a current pre-commit reduction check: task-owned additions are justified or simplified, with preserved contracts and renewed affected proof.
- `PASS` has current proof and scoped acceptance; missing independence or proof remains explicit.
- Authorized revisions receive renewed affected checks and verdicts.

## Procedure

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. In authorized code-change mode, require a reduction pass before each commit or final uncommitted handoff: compare the complete task delta with its verified baseline, including earlier task commits, staged, unstaged, and new files. Challenge additions with deletion, reuse, consolidation, or a narrower change at the existing owner. Have the caller apply supported reductions, not merely recommend them; justify retained complexity against the current contract and maintainability. Preserve required features, compatibility, security, failure handling, meaningful test detection, and unrelated or mixed-owner edits. Uncertain attribution or necessity is a gap, not permission to delete. Fewer lines alone, minification, hidden work, and deletion quotas are not success. Rerun invalidated checks and renew affected review after reductions; reuse current proof rather than repeat unchanged passes. Read-only work assesses or proposes, never performs code cleanup. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
Expand Down
Loading
Loading