AI-agent guides

What these files doCopy Anchor Link

Basestack publishes plain Markdown that helps a coding assistant choose a Feature Flags SDK, use the correct runtime imports, and implement safe fallbacks. These files supply integration knowledge. They do not grant account access, install an SDK, create a flag, or authorize production changes.

The guides work without MCP. They record reviewed package versions and dates; ask your assistant to inspect your installed versions before applying examples.

Start with a URLCopy Anchor Link

• Discovery index
• Feature Flags skill
• React reference
• Server frameworks and hydration

The .md links are public raw Markdown assets on the docs site, not rendered HTML pages under /content. They do not require a login or JavaScript.

Ask a browsing-capable assistant to fetch and read the skill and only the references relevant to your task. Pasting a URL alone does not guarantee that its contents enter the assistant's context. The llms.txt index follows an emerging community discovery convention, not a universal loading mechanism.

Read https://docs.basestack.co/skills/basestack-feature-flags/SKILL.md and the
references relevant to this repository. Inspect my framework, runtime, and
installed SDK versions before choosing imports. Integrate my existing
new-checkout flag with disabled/error fallbacks and tests for enabled,
disabled, missing, and unavailable states. Keep write tokens server-side.
Do not create or toggle production resources without asking.

Provide the actual project/environment selection and slug through your normal project configuration. Do not paste private API or MCP tokens into a prompt.

Attach a local fileCopy Anchor Link

If the assistant cannot fetch URLs, download the curated handbook and explicitly attach or include it using your tool's file/context feature. This is a curated Feature Flags and Forms handbook, not a full export of every Basestack page.

Choose a fresh filename in a directory you select, or review changes before replacing an existing copy:

curl --fail --location \
  "https://docs.basestack.co/llms-full.txt" \
  --output basestack-agent-context.md

This downloads text only. Never pipe it into a shell. Review the file, attach it, then specify the framework, runtime, installed versions, flag slug, and fallback you want. Saving a file does not automatically load it into every client. The handbook includes the referenced technical bodies, so offline reading does not require following remote companion links.

Reusable project instructionsCopy Anchor Link

Merge a short rule into your existing instructions if your client supports them. Do not replace AGENTS.md, CLAUDE.md, or any existing rules file.

For Basestack Feature Flags tasks, read the reviewed local Basestack context
attached to this project, or fetch https://docs.basestack.co/llms.txt and then the
Feature Flags skill and relevant references if network tools are available.
Inspect installed SDK versions and use the correct client/server imports.
Use disabled/error fallbacks. Never expose private API/MCP tokens or change
production resources without my approval. If context cannot be loaded, ask
me to attach it instead of guessing an API.

Optional portable skill installationCopy Anchor Link

For clients supporting the Agent Skills format, basestack-feature-flags/SKILL.md and its references/ files form a portable skill directory. A hosted URL is not an automatic installation. Downloading only SKILL.md is insufficient for offline references; copy the whole selected directory, preserving relative paths.

Use your selected client's official documentation for its supported local skill location and installation procedure. No client-specific installer command is prescribed here. When support is unclear, use the universal fetch/attach workflow above instead of assuming a client discovers remote URLs or follows every link.

Choose your contextCopy Anchor Link

• Index: discover the available product guides and references.
• Skill: integration instructions and SDK selection.
• Reference: one task's detailed contract, such as OpenFeature or React.
• Handbook: bulk context for attachment/offline use; avoid loading all of it by default when the assistant can fetch focused files.

The skill also routes to JavaScript (including Vue/Svelte wrappers), OpenFeature, the Vercel Flags SDK adapter, preview Web Components, the code-reference CLI, and REST reads. Each has different options and caching behavior.

Example tasksCopy Anchor Link

For a React SPA:

Use the Feature Flags skill and React reference. Inspect this Vite app's
React and SDK versions, reuse its existing provider, and gate new-checkout
with /client imports, loading UI, a disabled fallback, and payload validation.
Add mocked failure tests. Do not send private tokens to the browser.

For Next.js server rendering:

Read the server-frameworks and React references. Evaluate new-checkout in
this Next.js App Router app with the released /server exports. If client
hooks need hydration, pass only reviewed public flags and evaluation keys.
Test unavailable responses and verify no private tokens or sensitive payloads
appear in HTML, serialized props, or client bundles. Explain cache freshness.

Security and troubleshootingCopy Anchor Link

• No network tools: attach the handbook explicitly; a pasted URL is not context.
• Missing references: attach the complete skill directory or the needed file.
• Wrong package version: compare installed exports/peers with the reference's release notes. The reviewed React package requires react >=19.2.7; do not upgrade React automatically to make a snippet fit.
• Wrong environment or stale values: confirm keys/slug, provider reuse, SDK TTL, and upstream caching. A client cache clear is not a CDN purge.
• Secrets: evaluation identifiers are not private write tokens. Keep private API/MCP tokens server-side. Browser-consumed payloads are not secret, and feature flags are not authorization controls.
• Unsupported behavior: do not invent targeting, percentage rollouts, streaming, management endpoints, or dedicated Vue/Svelte packages.
• Source upload: the CLI uploads snippets and repository metadata. Approve the destination and scoped paths before running it or adding it to CI.
• Stale local copy: check the last-reviewed date against the public skill; deliberately refresh and review local context after affected releases.

MCP is separateCopy Anchor Link

Public guides explain application integration; MCP, when released for your deployment, provides separately authenticated management tools. It is optional and does not make a private token safe to expose. This guide does not advertise pending MCP endpoints or installation instructions: use only the management documentation verified as released for your deployment. No MCP setup is required to use these URLs or attachments.