AI-agent guides

What these files doCopy Anchor Link

Basestack's public Markdown gives a coding assistant task-oriented context for HTML, fetch, React/Next.js, and Vue forms, including validation, files, webhooks, and email notifications. It supplies knowledge, not account access or an automatic SDK installation. There is no dedicated Forms SDK in this inventory.

The guides work without MCP. They do not create a form or authorize live submissions, notifications, or account changes.

Start with a URLCopy Anchor Link

• Discovery index
• Forms skill
• React/Next.js reference
• Webhook and email reference

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 an assistant with browsing/network tools to explicitly fetch the skill and only the needed references. A pasted URL does not guarantee the text was loaded. llms.txt is an emerging discovery convention, not a universal client feature.

Read https://docs.basestack.co/skills/basestack-forms/SKILL.md and its
React/Next.js and integration references. Add a contact form using the
endpoint I provide, JSON response mode, pending/success/error states, and
configured validation. Preserve input on failure. Explain webhook setup
and how to verify delivery separately. Do not assume Google Sheets or
another native connector exists, and do not send live submissions without asking.

Provide the real dashboard submission endpoint and field/rule names. Keep private account/API/MCP tokens out of the prompt and frontend code.

Attach a local fileCopy Anchor Link

If the assistant cannot fetch URLs, download the curated Feature Flags and Forms handbook, review it, then explicitly attach/include it with the client's file/context feature. It is not the entire documentation site and does not configure accounts.

Choose a fresh filename in a directory you select; review changes before replacing any existing local copy:

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

This downloads text, not executable setup. Never pipe it into a shell. Saving it is not the same as attaching it. After attachment, give the assistant your framework, redirect versus JSON behavior, field names, test endpoint, and delivery requirements. The technical reference bodies are included for offline reading, not left as missing companion-file dependencies.

Reusable project instructionsCopy Anchor Link

Merge this into your existing rules only if your client supports them. Never overwrite AGENTS.md, CLAUDE.md, or other project instructions.

For Basestack Forms tasks, read the reviewed local context attached to this
project, or fetch https://docs.basestack.co/llms.txt and then the Forms skill and
relevant references if network tools are available. Use standard HTML/HTTP,
not an invented Forms SDK. Verify mode=rest, configured rules, file limits,
and delivery boundaries. Never expose private API/MCP tokens, invent native
connectors, forward personal data, or send live submissions without my approval.
If documentation cannot be loaded, ask me to attach it.

Optional portable skill installationCopy Anchor Link

For clients that support Agent Skills, the basestack-forms/ directory contains SKILL.md plus focused references/. Copy the entire selected directory and preserve the relative paths for offline use. Downloading only SKILL.md leaves references unavailable.

A public URL is not an automatic skill install. Follow the selected client's official documentation for its supported installation procedure/location. No client-specific installer command is prescribed here; use fetch or attachment when support is unclear. Do not assume a particular client follows linked files.

Choose your contextCopy Anchor Link

• Index: discover available files.
• Skill: choose an integration and follow its safe workflow.
• Reference: task-specific details for HTML, JavaScript/REST, React/Next.js, Vue, validation/security/files, or verified integrations.
• Handbook: optional bulk context for offline/file-only clients. Prefer focused references when network fetching is available.

Example tasksCopy Anchor Link

For native HTML redirects:

Read the Forms skill and HTML reference. Build an accessible contact form
with named fields matching my configured rules and the endpoint I provide.
Use ordinary POST navigation and explain the success/error redirects.
Use my configured honeypot name, not an assumed magic field. Do not submit it yet.

For file uploads:

Read the JavaScript/REST and validation-security-files references. Add files
to this existing React form using FormData and mode=rest. Do not set a manual
multipart Content-Type. Check retention/uploads settings, the current 1 MiB
per-file and five-file total limits, and add mocked errors without sending data.
Explain which fields webhook/email delivery excludes.

Security and troubleshootingCopy Anchor Link

• No network tools: attach the handbook; ask the assistant to confirm it can read the attached text instead of guessing from a URL.
• Missing references or stale local copies: copy the whole skill directory or attach the relevant files, check last-reviewed dates, and refresh deliberately.
• Wrong endpoint/environment: use the real dashboard key and a non-production form for approved tests. Accept alone does not select JSON; use ?mode=rest.
• Wrong package/API version: Forms uses HTML/HTTP, not an unpublished package. Compare self-hosted deployment behavior to the reviewed /v1 source contract.
• Rules or uploads fail: match exact field names, enabled/security settings, retention, and file limits. Preserve input; avoid automatic ambiguous retries.
• Secrets and privacy: never expose private API/MCP tokens. Client validation and CORS do not prevent all abuse. Submission data in query strings can leak.
• Unsupported connectors: webhook POST and configured email are covered; native Google Sheets/Slack/Discord are unverified. Do not invent their setup.
• Delivery: an accepted response is not proof of email/webhook delivery. The current webhook sender has no signature or stable event ID and can retry or duplicate. Review receiver access and consent before forwarding data.

MCP is separateCopy Anchor Link

The public guides explain integration; MCP, when released for your deployment, is a separately authenticated management capability. It is optional and does not replace the HTTP submission contract or authorize notifications. This guide does not advertise pending endpoints: use only management documentation verified as released for your deployment. Fetch/attach workflows need no MCP setup.