Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

assets-governance

Étoiles5

Forks0

Mis à jour13 mai 2026 à 06:06

Use when creating or maintaining OpenArc asset structure under docs/assets for brand files, icons, illustrations, screenshots, and references.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Yipxiyi

Yipxiyi/OpenArc

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

SKILL.md

readonly

name	assets-governance
description	Use when creating or maintaining OpenArc asset structure under docs/assets for brand files, icons, illustrations, screenshots, and references.

Assets Governance

Use this skill when a repository needs structured asset organization for design, brand, or implementation continuity.

Goal

Keep assets discoverable and connected to governance docs.

Recommended Structure

docs/assets/
  brand/
  icons/
  illustrations/
  screenshots/
  references/

Directory Purpose

brand/: logos and identity assets
icons/: icon systems
illustrations/: illustration references
screenshots/: UI captures
references/: inspiration and competitor references

Rules

Do not create abstract-only documentation when concrete assets are available.
Make docs/DESIGN.md and docs/BRAND.md reference relevant asset directories.
Preserve existing asset organization when it is already coherent.
Avoid moving large asset sets unless the user explicitly asks for migration.

Plus depuis ce dépôt

même dépôt

clarification-gate

Yipxiyi/OpenArc

Use when a new goal, feature request, migration, or non-trivial change needs focused clarification before PRD, spec, plan, or implementation work begins.

2026-07-105

implementation-workflow

Yipxiyi/OpenArc

Use when implementing repository changes through the smallest safe path, from direct routine fixes to risk-driven clarification, specs, plans, task coordination, validation, and documentation updates.

2026-07-105

openarc

Yipxiyi/OpenArc

Use when a user asks to use OpenArc generally, initialize governance, improve repository continuity, audit governance drift, migrate an existing workspace, or choose which OpenArc skill should handle a request.

2026-07-105

planning-engine

Yipxiyi/OpenArc

Use when producing a lightweight implementation plan before coding, including scope, affected systems, migration, rollback, tests, reuse, and architecture impact.

2026-07-105

repository-governance

Yipxiyi/OpenArc

Use when auditing repository governance read-only, or when explicitly initializing or repairing governance and patching an agent guide without destructive rewrites.

2026-07-105

spec-workflow

Yipxiyi/OpenArc

Use when creating or updating OpenArc feature specs with acceptance criteria, compatibility decisions, and technical direction.

2026-07-105

name	assets-governance
description	Use when creating or maintaining OpenArc asset structure under docs/assets for brand files, icons, illustrations, screenshots, and references.

Assets Governance

Use this skill when a repository needs structured asset organization for design, brand, or implementation continuity.

Goal

Keep assets discoverable and connected to governance docs.

Recommended Structure

docs/assets/
  brand/
  icons/
  illustrations/
  screenshots/
  references/

Directory Purpose

brand/: logos and identity assets
icons/: icon systems
illustrations/: illustration references
screenshots/: UI captures
references/: inspiration and competitor references

Rules

Do not create abstract-only documentation when concrete assets are available.
Make docs/DESIGN.md and docs/BRAND.md reference relevant asset directories.
Preserve existing asset organization when it is already coherent.
Avoid moving large asset sets unless the user explicitly asks for migration.