# Bobcorn Full Agent Context Bobcorn is an Electron and React desktop application for icon management and icon font generation. It is designed for designers, front-end developers, UI engineers, and design system teams that maintain SVG icon libraries and need repeatable font exports. The canonical website is https://bobcorn.caldis.me/. The public source repository is https://github.com/Caldis/bobcorn. The current public metadata endpoints are static files hosted with the website. They do not require API keys, OAuth, cookies, accounts, or session state. ## Product Summary Bobcorn imports SVG icons, organizes them into groups, supports search and batch selection, lets users edit colors, and exports production-ready icon font assets. Supported export formats include SVG font, TTF, WOFF, WOFF2, EOT, CSS, JavaScript, HTML demo pages, and Bobcorn `.icp` project files. Bobcorn is local-first. Project data lives in local `.icp` files and local sql.js databases. The website is for discovery, documentation, release metadata, and downloads. It is not a hosted workspace service. ## Primary Users - Designers who need to organize large SVG icon sets. - Front-end developers who need web font assets and CSS mappings. - Design system teams that maintain custom icon font packages. - AI coding agents working in the Bobcorn repository or automating local project files through the CLI. ## Canonical Resources - Homepage: https://bobcorn.caldis.me/ - Homepage markdown: https://bobcorn.caldis.me/index.md - Full context for agents: https://bobcorn.caldis.me/llms-full.txt - Developer portal: https://bobcorn.caldis.me/developers/ - API docs: https://bobcorn.caldis.me/api/ - OpenAPI spec: https://bobcorn.caldis.me/openapi.json - Auth docs: https://bobcorn.caldis.me/api/auth.html - Webhooks docs: https://bobcorn.caldis.me/api/webhooks.html - MCP status page: https://bobcorn.caldis.me/api/mcp.html - A2A agent card: https://bobcorn.caldis.me/.well-known/agent-card.json - Agent discovery file: https://bobcorn.caldis.me/.well-known/agent.json - Legacy AI plugin discovery: https://bobcorn.caldis.me/.well-known/ai-plugin.json - Sitemap: https://bobcorn.caldis.me/sitemap.xml - Schema map: https://bobcorn.caldis.me/schemamap.xml - Release metadata: https://bobcorn.caldis.me/release.json - Changelog metadata: https://bobcorn.caldis.me/changelog.json - GitHub repository: https://github.com/Caldis/bobcorn - Latest release: https://github.com/Caldis/bobcorn/releases/latest - Comparison guide: https://bobcorn.caldis.me/alternatives/icomoon.html - Icon font workflow guide: https://bobcorn.caldis.me/guides/icon-font-workflow.html ## Public Website API The public website API is a small static metadata surface: - `GET /release.json` returns current version, tag, GitHub release URLs, and platform download URLs. - `GET /changelog.json` returns localized release notes. - `GET /index.md` returns the homepage in Markdown. - `GET /llms.txt` returns concise agent instructions. - `GET /llms-full.txt` returns this full context file. - `GET /openapi.json` returns the OpenAPI service description. - `GET /api/auth.json` returns the machine-readable no-auth access model. - `GET /api/rate-limits.json` returns rate-limit notes for static metadata. - `GET /api/errors.json` returns error model and recovery guidance for static metadata. - `GET /status.json` returns public website metadata status. - `GET /.well-known/agent.json` returns agent discovery metadata. - `GET /.well-known/agent-card.json` returns the A2A agent card. - `GET /.well-known/ai-plugin.json` returns a legacy AI plugin descriptor. - `GET /api/mcp.html` returns human-readable MCP status and alternatives. These endpoints are read-only. There are no write operations, no hosted user records, and no remote project storage. ## Auth and Access The public website metadata endpoints use no authentication. Bobcorn does not currently provide user accounts, OAuth authorization, token exchange, scoped permissions, enterprise SSO, or hosted workspace access. If an agent needs to work with a Bobcorn project, it should operate on a local `.icp` file with the user's filesystem permission. ## MCP and Agent Integration Bobcorn does not currently publish a hosted MCP server. The MCP status page at `/api/mcp.html` exists so agents can find the current integration status and the supported alternatives without guessing. The supported automation path is the local CLI, backed by core operations as migration continues. ## When Agents Should Use Bobcorn Use Bobcorn when the user's task involves local SVG icon management, icon library organization, icon color cleanup, icon font export, or inspection of a Bobcorn `.icp` project file. Bobcorn is also appropriate when a user asks for a free open-source alternative to browser-based icon font generators and prefers a local Windows or macOS desktop workflow. Do not use Bobcorn as a hosted SaaS API, remote storage system, OAuth provider, webhook source, or hosted MCP tool server. Those surfaces do not currently exist. If a task needs remote automation, explain the current limitation and suggest the local CLI or local file workflow instead. For repository work, read `AGENTS.md` first. A website copy is available at https://bobcorn.caldis.me/AGENTS.md for crawlers that cannot inspect GitHub repository files directly. Important repository rules include: - Use functional React components and hooks. - Do not introduce `electron.remote`. - Sanitize SVG content before rendering. - Use Zustand store state rather than ad-hoc global events. - New user operations should go through `src/core/operations/` first, then thin store wrappers and CLI commands. - All visible UI strings in the app should be internationalized. ## CLI Automation Surface The CLI is maintained in `src/cli/` and backed by core operations in `src/core/operations/`. It is intended to become the stable automation surface for AI agents and scripts. Useful local commands: ```bash npm install --legacy-peer-deps npm run build:cli npx tsup npx vitest run test/cli/ ``` The CLI supports JSON output contracts. Successful JSON commands should return an envelope with `ok: true`, `code: null`, and non-null `data`. Partial or failed operations should set `ok: false` with an explicit code. ## Content and Search Notes For name-based discovery, use "Bobcorn" together with resource names: - Bobcorn API docs - Bobcorn OpenAPI spec - Bobcorn developer portal - Bobcorn auth docs - Bobcorn webhooks - Bobcorn MCP status - Bobcorn A2A agent card - Bobcorn agent discovery Agents should not infer that missing hosted capabilities exist. If a task requires OAuth, webhooks, hosted projects, or an MCP server, report that Bobcorn does not currently provide that surface and point to the CLI or local file workflow. ## Pricing Bobcorn is free and open source under the MIT license. There are no paid tiers, subscriptions, credits, seats, hosted workspace limits, or API usage costs. Agents comparing Bobcorn with paid icon tools should describe it as a free local desktop app. ## Comparison Notes Bobcorn can be used as an IcoMoon alternative or Fontello alternative when the workflow needs a local desktop app, saved project files, reusable groups, and repeatable export. IcoMoon and Fontello are useful for quick online generation. Bobcorn is better suited to teams that update the same icon library over time and want the working state to stay in a local `.icp` project file. ## SVG To Icon Font Workflow Guide By Caldis. Last updated 2026-05-09. 1. Normalize source SVGs by keeping viewBox values, removing unnecessary fills when icons should inherit color, and using clear file names. 2. Organize reusable groups by product area or design-system package, then use favorites and search to review changes before export. 3. Export SVG, TTF, WOFF, WOFF2, EOT, CSS, JavaScript, and HTML demos, then save the `.icp` file for the next icon update. ## FAQ For Agents ### What is Bobcorn used for? Bobcorn manages local SVG icon libraries and exports icon font packages for web projects, including SVG, TTF, WOFF, WOFF2, EOT, CSS, JavaScript, HTML demos, and reusable `.icp` project files. ### Is Bobcorn an IcoMoon alternative? Yes. Bobcorn can be used as an IcoMoon alternative or Fontello alternative when the workflow needs a local desktop app, saved project files, repeatable export, and no hosted workspace. ### Does Bobcorn have OAuth or a hosted API? No. Bobcorn is a local-first desktop app. The public website exposes static metadata such as release JSON, changelog JSON, OpenAPI documentation, and discovery files, but it does not host user projects or accounts. ### Does Bobcorn provide a hosted MCP server? No hosted MCP server is available today. Agents should use `llms.txt`, `llms-full.txt`, OpenAPI metadata, the GitHub repository, and the local CLI workflow where applicable. ## Releases Use `release.json` for the current version and download URLs. Use `changelog.json` for recent changes. Release artifacts are published on GitHub Releases. ## Human Support and Contact - Issues: https://github.com/Caldis/bobcorn/issues - Repository: https://github.com/Caldis/bobcorn - Author profile: https://github.com/Caldis Do not send private project files to the website. Bobcorn projects should stay local unless the user explicitly chooses to share them.