Skill This
AI Skill Report Card

Building Design Knowledge Base

B+78·Feb 26, 2026·Source: Web
Quick Start15 / 15
knowledge-base/
├── brand-assets/
│   ├── logos/[version]/[context]/
│   ├── colors/[palette-name]/
│   ├── typography/[typeface]/[weights]/
│   └── imagery/[style]/[usage]/
├── decisions/[YYYY-MM-DD-decision-title].md
├── project-briefs/[client-project-name].md
├── communication-patterns/[scenario-type].md
└── retrospectives/[YYYY-QQ]/

Create first decision record:

Markdown
# 2024-01-15-primary-color-standardization.md
Recommendation▾
Add concrete metrics for knowledge base success (search times, reuse rates, decision confidence scores)
Context

Multiple blue variants across client projects causing brand inconsistency.

Decision

Standardize primary blue to #0066CC across all touchpoints.

Rationale
  • Improves brand recognition by 40% (user testing)
  • Reduces design decision fatigue
  • Enables systematic color palette scaling
Consequences

✅ Consistent brand presence ✅ Faster design iterations ❌ Requires updating 12 existing projects

Workflow13 / 15

Progress:

  • Asset Taxonomy Setup

    • Create version-controlled folders by asset type
    • Tag each asset: [version].[context].[format]
    • Document usage guidelines per asset

  • Decision Records (ADR)

    • Use YYYY-MM-DD-decision-title.md naming
    • Template: Context → Decision → Rationale → Consequences
    • Link related decisions and assets

  • Project Brief Templates

    • Include SEO keyword research section
    • Map keywords to visual direction
    • Template reusable components

  • Communication Patterns

    • Document successful client interaction flows
    • Create templates for common scenarios
    • Track what messaging resonates

  • Quarterly Retrospectives

    • Review decision outcomes
    • Update knowledge gaps
    • Refine search taxonomy
Recommendation▾
Include template for the project-briefs mentioned in workflow - currently referenced but not provided
Examples16 / 20

Example 1: Input: New project needs brand colors Output: Search "colors/primary" → Returns #0066CC with usage context, decision rationale, and 3 successful implementation cases

Example 2: Input: Client pushes back on typography choice Output: Reference communication-patterns/typography-objections.md → "Here's why this typeface supports your conversion goals..." (proven script)

Example 3: Input: Quarterly team review Output: retrospectives/2024-Q1/ shows 15 decisions made, 8 validated, 2 need revision, knowledge gaps in mobile imagery

Recommendation▾
Specify integration points with existing design tools (Figma, Notion, etc.) and technical implementation details
Best Practices

Tagging System:

  • Assets: [brand].[version].[context].[format] (apple.v2.mobile.svg)
  • Content: Use consistent keywords across all documents
  • Link decisions to affected assets and projects

Search Optimization:

  • Front-load titles with searchable terms
  • Include synonyms in metadata
  • Cross-reference related concepts

Version Control:

  • Never delete old versions, mark deprecated
  • Document migration paths between versions
  • Track which projects use which versions

Knowledge Capture:

  • Record decisions immediately after making them
  • Include measurable outcomes where possible
  • Document both successes and failures
Common Pitfalls

❌ Generic file names - Use specific, searchable titles ❌ Missing context - Always explain WHY decisions were made ❌ Orphaned assets - Link every asset to its decision record ❌ Stale information - Regular audits prevent outdated knowledge ❌ Over-categorization - Keep taxonomy simple and intuitive ❌ Knowledge hoarding - Make contribution easy and rewarded

0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
15/15
Workflow
13/15
Examples
16/20
Completeness
16/20
Format
15/15
Conciseness
13/15
Save to My Skills