Guides
LiveGet started with Fygment
Create 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.
- Updated
- 2026-05-20
Start here when you need the shortest path from sign-in to a workspace that can import, review, install, and check governed AI Skills.
First setup path
The public launch path is intentionally narrow. Use this sequence before jumping into advanced governance or billing settings.
- 1
Sign in or accept an invite
Use the magic-link login flow. If you have an invite, open the invite link first so Fygment can attach the new session to the invited workspace.
- 2
Open or create a workspace
A workspace is the boundary for Skills, members, installs, approvals, support reports, and billing state. Pick personal for solo use or company for a shared pilot.
- 3
Import or create one Skill
Start with one concrete Skill instead of a large library. Fygment validates package shape and keeps review state explicit before install.
- 4
Connect a harness
Use the MCP setup guide or the CLI setup command to connect Codex, Claude-family tools, or hosted MCP clients to the workspace.
Launch boundary
Treat Live, Alpha, Manual, and Gated labels literally
Live means the workflow is part of the controlled public launch surface. Alpha means usable but still being hardened. Manual means supported by an owner/admin or support workflow. Gated means do not depend on it until the named evidence or configuration is complete.
Related docs
- Workspaces, members, and access
A workspace is the unit of trust in Fygment. Membership, role, invite, install, report, and billing behavior all resolve through that boundary.
- Import Skills
Import 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.
- Set up Fygment MCP
MCP 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.