Help us improve
Share bugs, ideas, or general feedback.
From policystack
Scaffolds PolicyStack in a project: runs the @policystack/cli installer and wires the single <PolicyStack> provider for privacy policy and consent banner.
npx claudepluginhub jamiedavenport/policystack --plugin policystackHow this skill is triggered — by the user, by Claude, or both
Slash command
/policystack:policystack-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- Generated by @policystack/sdk renderSkillPack() — do not edit by hand. Run `vp run gen`. -->
Audits a policystack.ts config by running validation, explaining each issue code, and proposing minimal fixes until clean. Use when PolicyStack config has validation errors or warnings.
Generates Korean legal documents (privacy policy, terms of service, cookie banner, consent modal) for Next.js App Router projects based on Korean privacy and e-commerce laws, using kimlawtech/korean-privacy-terms as upstream.
Generates privacy policies and terms of service tailored to project stack, features, and data handling. Audits data practices for GDPR, CCPA, app store compliance.
Share bugs, ideas, or general feedback.
Set PolicyStack up in an existing project. PolicyStack generates a privacy
policy, a cookie policy, and the consent runtime from one typed
defineConfig() call. It is not legal advice — a lawyer should review the
output before publication.
npx @policystack/cli@latest init
init detects the package manager and framework from package.json,
installs @policystack/sdk plus the right framework integration, scaffolds a
starter policystack.ts (src/policystack.ts when a src/ directory
exists, else the project root), writes policystack.llms.txt next to it, and
prints a setup prompt. Useful flags: --cwd, --pm, --skip-install,
--dry-run, --yes, --out, --force.
If init cannot run, install by hand: @policystack/sdk always, plus
@policystack/vite and the framework package (@policystack/react, …).
policystack.tsRead the generated policystack.llms.txt — it is the type-accurate SDK
reference (jurisdiction ids, lawful bases, presets) for this exact version.
The canonical, commented reference config is
examples/tanstack/src/policystack.ts.
jurisdictions is required and non-empty. Valid ids (frozen at 1.0):
br, ca, ch, eea, row, uk, us, us-ca, us-co, us-ct, us-va. Any unlisted us-<state> falls back to us. Pick the
codes that actually apply; policystack-jurisdiction explains the posture
each implies.
Wrap the app root once with the single provider — it supplies both the policy context and the consent store (derived from the same config):
import { PolicyStack } from "@policystack/react/provider";
import config from "./policystack";
export function App({ children }: { children: React.ReactNode }) {
return <PolicyStack config={config}>{children}</PolicyStack>;
}
<PrivacyPolicy> / <CookiePolicy>, useConsent, and ConsentGate
all read from it. Components ship unstyled and emit data-op-* attributes.
For non-React frameworks use that framework's @policystack/<fw> package.
Run policystack-audit (policystack validate --json) and resolve every
issue before shipping. Annotate real data flows with policystack-instrument
so the policy reflects what the code actually does.