design-note

Generate Japanese design notes with intent, architecture, components, and acceptance criteria.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/refluster/ai-native-article --skill design-note-refluster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-note
Source: https://github.com/refluster/ai-native-article/tree/main/workforce/skills/design-note
Command: npx skills add https://github.com/refluster/ai-native-article --skill design-note-refluster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of design notes in Japanese, capturing intent, information architecture, components, and acceptance criteria for UI or visual-system changes, enhancing collaboration and review processes.

Core Features & Use Cases

  • Design Decision Documentation: Captures design decisions in a reviewable form for UI or visual-system changes.
  • Japanese Language Support: Generates design notes in Japanese, catering to the specific language needs of the design team.
  • Structured Format: Ensures consistency across design notes with dedicated sections for intent, information architecture, components, and acceptance criteria.
  • Use Case: When a Designer persona needs to document a design decision for a UI or visual-system change before implementation begins, this Skill provides the necessary framework.

Quick Start

Use the 'design-note' skill to create a design note for your UI change, starting with defining the 'Intent'.

Frequently Asked Questions about design-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document UI design decisions for review in Japanese?

To document UI design decisions in Japanese, you need a structured design note capturing intent, information architecture, components, and acceptance criteria. This omits implementation details to facilitate team review processes.

What should be included in a visual-system design note?

A visual-system design note should include dedicated sections for design intent, information architecture, components, and acceptance criteria. It targets design decisions specifically, omitting implementation details.

Can I generate design documentation without including code implementation details?

Yes, you can generate design documentation without implementation details. The note focuses purely on UI and visual-system design decisions, separating design intent from technical implementation.

How do I structure acceptance criteria for a UI design change?

To structure acceptance criteria for a UI design change, use a standardized format pairing criteria with design intent and information architecture. This ensures visual-system requirements are reviewable before implementation.

Does this design documentation method support visual-system changes at scale?

The design documentation method supports visual-system changes by providing a consistent structured format. It captures information architecture and components, keeping design decisions reviewable across UI updates.