Marlan Yokomiso v0.8.26
Build and manage your brand.
From the developer
Not specified in the available declarations: pricing & account requirements.
Use my selected Perture brand to plan an on-brand interface after checking its readiness.
Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 6, 2026.
From the marketplace listing
Connect ChatGPT and Codex to your Perture Brand Pages: approved colors, typography, logos, visual references, interface components and output guidance. Build and review brand-aware work with the current Perture skill and its bundled validation resources. On supported coding hosts, local checks help verify source and rendered interfaces. Authorized owners can explicitly request scoped Brand Page edits, component and variant authoring, file uploads and agent/Figma sync settings. Requires an eligible Perture account; editing availability depends on account permissions. Generated source submitted for remote verification and selected files for upload are sent to Perture over HTTPS. Unrelated repository files stay local. Draft edits, Brand Release publication, saving Works and deployment are separate actions that require the user's corresponding request.
Language: English · Automatically detected from descriptions.
· 3 observations
Logo url dark changed from “https://files.openai.com/content?id=file_0000000045f8820e863620e84806a3aa” to “https://files.openai.com/content?id=file_00000000dd7c820e821a97b5cbf722f8”. Privacy policy url changed from “https://app.perture.co/privacy” to “https://perture.co/privacy”. Terms of service url changed from...
View comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Agent skills for building with Uniform: Next.js integration, content and experience modeling, navigation, forms, automations, assets, and...
Shared terms: coding, component, guidance, repository
the brand id lets authenticated users connect their live brand profile to ChatGPT. The plugin returns read-only brand context, copy guida...
Shared terms: brand, guidance, visual, context
Create, edit, preview, publish, and manage lightweight web projects with Prot0.
Shared terms: approved, component, submitted, action
Create and retrieve brand-aware blog posts and landing pages from a structured brief.
Shared terms: brand, aware, publication, separate
BrightSite is a website hosting and content management platform. Connect your BrightSite account to build and edit pages, layouts, and re...
Shared terms: component, deploy, setting, upload
--- name: perture description: Use a connected Perture brand for local frontend work, external host outputs, or explicitly requested Brand Page edits. --- # Perture Design Agent Use Perture as the source of brand intent and the local repository as the source of implementation context. Preserve the user's product behavior, content, permissions and chosen architecture. ## Select one mode - **External output**: the user asks another host such as Sites, Canva or ChatGPT to create a page, design or document using Perture Brand Page references. Use the read-only reference workflow below. A page created in Sites is an external output even though its result is frontend UI. - **Build**: the user asks to create or change frontend UI in a local repository. Read [references/build.md](references/build.md). - **Review**: the user asks whether existing UI follows the Perture brand. Read [references/review.md](references/review.md). Repository access stays read-only. - **Fix**: the user asks to repair Perture findings. Read [references/fix.md](references/fix.md). - **Brand Editor**: the Pro owner asks to add or edit Brand Page colors, typography, logos, fonts, illustrations, spacing or rounding. Read [references/brand-editor.md](references/brand-editor.md). This mode does not require a frontend repository or `prepare_ui_change`. Build includes a scoped post-build review only when `automatic_reviews` is enabled in the returned account behavior. Its safe repair loop also requires `automatic_corrections`. Do not treat either automation as authorization for unrelated cleanup. If the request is ambiguous between Review and Fix, begin with Review and obtain authorization before any edit. For Build, Review and Fix modes that run deterministic checks, read [references/local-validation.md](references/local-validation.md) before running the bundled validator. ## External output workflow 1. Use the connected Perture app to call `list_brands`, select the exact brand with `set_active_brand`, and retain its `brand_lock_token`. 2. Before invoking Sites, another generator, or writing output source, call `preflight_brand_output` with the exact output type. Include every capability explicitly requested by the user in `required_capabilities` (for example `illustration`, `photography`, `iconography` or `pattern`). A `blocked` result ends generation: report its short `blocked_reasons` and ask the brand owner to complete those Brand Page fields. Do not invent a missing style, use an unrelated asset, choose a different brand, or try a generic host fallback. The allowed hex list is exact; deriving lighter or darker shades is not authorized. A `ready` result with `visual_authorized: false` permits only an output without a new visual; `illustration_authorized: false` never permits drawing a new illustration or substituting an unrelated asset. Follow `visual_execution` when it is present. `official_asset` allows only the mapped image unchanged. `generate_from_references` requires a new original image guided by the returned reference images; those images are inputs, not finished assets. If image generation cannot use the references as visual inputs, stop and report the missing capability. A CSS product mockup does not fulfill a required illustration. This is a deterministic check before model-heavy generation, not a second model review. If this tool is unavailable, stop and report an incompatible Perture MCP version. 3. On `ready`, call `get_brand_reference_for_output` once with the actual output type, logo background and available space. It includes the output guidance, complete color list, logo choice and visual references. Use only the returned official assets and brand guidance. Call `get_output_reference` only if a specific field is absent from this package. For frontend work, call `plan_brand_interface` once with every meaningful role: controls, containers,
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 13 — file references are metadata, not package contents.
Update to the completed Perture skill with its supporting references and local validation scripts. Add explicit Pro Brand Page authoring and settings capabilities. The MCP catalog exposes individually named operations for snapshot items, sections, guidance, Interface System components/variants, uploads and legacy logo reconciliation, with corrected overwrite annotations. Read access remains scoped; editing requires Pro ownership, exact brand selection, OAuth write authorization, version checks and verified saves. Existing walkthrough covers brand-context reads; editor test cases are provided separately.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 6, 2026.
plugin_asdk_app_6acac485f3648191a034ab7764e51198
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.
