Documentation
Fygment docs for real product use.
Set up a workspace, import or create Skills, review and approve packages, connect Codex or Claude-family tools, configure MCP, and troubleshoot launch-critical workflows without bouncing through marketing pages or authenticated dead ends.
Start here
First useful path
- 1
Get started with Fygment
LiveStart here when you need the shortest path from sign-in to a workspace that can import, review, install, and check governed AI Skills.
Open guide - 2
Import Skills
AlphaImport turns an existing Skill into a validated Fygment package. Start with one selected package or public source and review the validation result before broader migration.
Open guide - 3
Review and approve Skills
LiveGovernance is the difference between a shared Skill library and a loose pile of files. Review decisions decide what can be installed and trusted.
Open guide - 4
Set up Fygment MCP
AlphaMCP setup gives AI clients access to workspace-scoped Fygment tools. Hosted clients use OAuth; local clients use guided setup and a local authenticated proxy where needed.
Open guide
Guides
Guides
Task-oriented product documentation for setup, Skills, installs, and MCP.
Get started with Fygment
LiveCreate a workspace, understand the launch boundary, and reach the first useful Fygment workflow without guessing where to click.
Audience: New users, pilot workspace owners, and teammates joining an existing workspace.
Import Skills
AlphaImport Skill packages, Skill files, and supported public sources while keeping validation, provenance, and review state explicit.
Audience: Users moving local or public Skills into a governed workspace.
Create a Skill
AlphaStart a valid draft Skill from a template, then add instructions and metadata before review or publication.
Audience: Vibecoders, super-users, and workspace builders creating new Skills.
Review and approve Skills
LiveUse lifecycle states, proposal review, version decisions, and owner/admin approvals to keep install decisions clear.
Audience: Owners, admins, maintainers, and reviewers managing Skill lifecycle.
Install Skills in Codex
AlphaUse Fygment CLI setup, install, check, and update flows for Codex-targeted Skill usage.
Audience: Codex users who want workspace-approved Skills in their local harness.
Install Skills in Claude-family tools
AlphaUse Fygment setup and install/check flows with Claude Code and Claude-family harnesses where the current pilot supports writable targets.
Audience: Claude Code and Claude-family users using Fygment-managed Skills.
Set up Fygment MCP
AlphaConnect hosted MCP clients or local editors to the Fygment MCP endpoint without exposing tokens or workspace-private data.
Audience: Users connecting Claude, ChatGPT, Manus, Perplexity, local editors, or CLI clients to Fygment MCP.
Concepts
Concepts
Core product concepts that explain how Fygment scopes trust, access, and workflow state.
Reference
Reference
Command and interface references for users wiring Fygment into real local workflows.
Troubleshooting
Troubleshooting
Safe checks and report guidance when imports, setup, MCP, or access do not behave as expected.
Release And Launch Status
Release And Launch Status
Billing, privacy, and trust boundaries for controlled public launch.
Billing and launch mode
ManualUnderstand Fygment manual billing, Stripe test-mode foundation, and the gates before self-serve paid billing is live.
Audience: Workspace owners, admins, and launch reviewers deciding how billing should behave during public launch.
Security and privacy boundaries
ReferenceWhat Fygment does and does not expose in public launch docs, support reports, admin views, imports, MCP, and billing metadata.
Audience: Workspace operators, support reviewers, and users checking trust boundaries.
Product docs explain how to use Fygment. Resources are for broader articles and category thinking. Roadmap, Status, Privacy, Terms, and Support remain public references, but launch-critical product use should start here.