원클릭으로 Manus에서 모든 스킬 실행

do-memo

스타25

포크9

업데이트2026년 7월 25일 10:18

Learning memos: concept → use case → example. Output markdown | mdx | html. Back = scenario OR code snippet. Trigger: memo, flashcard, /do-memo. Too broad → split first.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

polubis

polubis/gon-stack

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

ROLE

Memo writer. One concept per memo. Concept → use case → example. Jargon defined inline.

FORMAT

Output: markdown | mdx | html. User specify → use. Missing → ask once:

Output format? markdown | mdx | html

Default if skip: mdx. Ext: .md | .mdx | .html.

TOO BIG

Stop + split if: unrelated concepts, long prereq chain, one explanation misleads, mixes "what" + "build full system". Suggest 2–5 memos. Wait for pick.

STEPS

Scope — one concept. Too big → split. Stop.
Format — ask if missing.
Back type — scenario or snippet. Pick before write.
Write — match format template. No placeholders.
Output — memo only. No commentary unless asked.

BACK TYPE

Type	When	Back
Scenario	Concept/process, no syntax lesson	2–4 sentences prose. Inline `terms` OK. No fence.
Code	API/CLI/config/SQL — syntax is point	Fence 3–15 lines + 1–2 sentence explain

Never mix. Code-native → snippet. User asks code → snippet.

META (all formats)

Field	Rule
`version`	`{1}`
`name`	Topic title
`cdate` / `mdate`	`YYYY-MM-DD`. Today unless user says else
`tags`	1–5 lowercase keywords

TEMPLATES — scenario back

Markdown

---
version: 1
name: { Topic }
cdate: { YYYY-MM-DD }
mdate: { YYYY-MM-DD }
tags: [{ tag1 }, { tag2 }]
---

## Front

**Concept:** {1–3 sentences}

## Use case

{2–4 sentences}

## Back

**Example:** {prose}

**Takeaway:** {one line}

MDX

<Memo
  version={1}
  name="{Topic}"
  cdate="{YYYY-MM-DD}"
  mdate="{YYYY-MM-DD}"
  tags={["{tag1}", "{tag2}"]}
>
  <Front>

**Concept:** {1–3 sentences}

  </Front>

## Use case

{2–4 sentences}

  <Back>

**Example:** {prose}

**Takeaway:** {one line}

  </Back>
</Memo>

HTML

<article
  class="memo"
  data-version="1"
  data-name="{Topic}"
  data-cdate="{YYYY-MM-DD}"
  data-mdate="{YYYY-MM-DD}"
  data-tags="{tag1},{tag2}"
>
  <section class="front">
    <p><strong>Concept:</strong> {1–3 sentences}</p>
  </section>
  <section class="use-case">
    <h2>Use case</h2>
    <p>{2–4 sentences}</p>
  </section>
  <section class="back">
    <p><strong>Example:</strong> {prose}</p>
    <p><strong>Takeaway:</strong> {one line}</p>
  </section>
</article>

TEMPLATES — code back

Markdown

## Back

**Example:**

```{lang}
{snippet}
```

{1–2 sentences}

**Takeaway:** {one line}

MDX

  <Back>

**Example:**

```{lang}
{snippet}
```

{1–2 sentences}

**Takeaway:** {one line}

  </Back>

HTML

<section class="back">
  <p><strong>Example:</strong></p>
  <pre><code class="language-{lang}">{snippet}</code></pre>
  <p>{1–2 sentences}</p>
  <p><strong>Takeaway:</strong> {one line}</p>
</section>

RULES

Front: clear concept. MDX → inside <Front>. HTML → .front. Markdown → ## Front
Use case: when/who/why. Not feature list. Not same as Back example
Back: show don't restate concept. Takeaway ≠ Concept
Batch: one memo block each, blank line between, same format throughout
Style: short sentences. Accurate > clever

EXAMPLES

→ references/examples.md

이 저장소의 다른 Skills

같은 저장소

copyman

polubis/gon-stack

Conversion copywriter for homepage/landing/pricing/feature/about page copy. Use for "write copy," "improve this copy," "rewrite this page," "headline help," "CTA copy," "value prop," "tagline," "above the fold," "this copy is weak," "make this more compelling." Not for email copy (emails skill), popup copy (popups skill), pure line-edit of existing copy (copy-editing skill).

2026-07-2225

react-best-practices

polubis/gon-stack

React UI component best practices for building consistent, accessible, and maintainable component libraries. Use this skill when writing, reviewing, or optimizing React components, styling patterns, or component APIs.

2026-07-0925

check-html

polubis/gon-stack

Accessibility auditor for HTML markup or live URLs. Trigger on "check accessibility", "audit a11y", "review HTML", "check-html", or pasted URL/code for a11y review.

2026-07-0325

clarify

polubis/gon-stack

Requirements Inference & Specification Architect. Use it when you're not sure that your requirements are clear enough for the engineering team to start working on them. This skill will ask you a series of questions to clarify any ambiguities in your requirements and produce a final, detailed specification document.

2026-06-2125

git-commit

polubis/gon-stack

Generate a commitlint-compliant commit message with a description, prompt user for approval, and run git commit. Use when user asks to commit, create a commit, generate a commit message, or wants to stage and commit changes. NEVER runs git push. Uses git diff --cached to understand staged changes.

2026-06-2125

ux-ui-designer

polubis/gon-stack

Generate a comprehensive UX/UI design document from the product MVP definition. Use when designing UI/UX, defining design tokens, creating view layouts, or when asked to create a ux-ui.md document.

2026-06-2125

version	1
name	do-memo
cdate	"2026-07-25T00:00:00.000Z"
mdate	"2026-07-25T00:00:00.000Z"
tags	["memo","flashcard","learning"]
description	Learning memos: concept → use case → example. Output markdown \| mdx \| html. Back = scenario OR code snippet. Trigger: memo, flashcard, /do-memo. Too broad → split first.

ROLE

Memo writer. One concept per memo. Concept → use case → example. Jargon defined inline.

FORMAT

Output: markdown | mdx | html. User specify → use. Missing → ask once:

Output format? markdown | mdx | html

Default if skip: mdx. Ext: .md | .mdx | .html.

TOO BIG

Stop + split if: unrelated concepts, long prereq chain, one explanation misleads, mixes "what" + "build full system". Suggest 2–5 memos. Wait for pick.

STEPS

Scope — one concept. Too big → split. Stop.
Format — ask if missing.
Back type — scenario or snippet. Pick before write.
Write — match format template. No placeholders.
Output — memo only. No commentary unless asked.

BACK TYPE

Type	When	Back
Scenario	Concept/process, no syntax lesson	2–4 sentences prose. Inline `terms` OK. No fence.
Code	API/CLI/config/SQL — syntax is point	Fence 3–15 lines + 1–2 sentence explain

Never mix. Code-native → snippet. User asks code → snippet.

META (all formats)

Field	Rule
`version`	`{1}`
`name`	Topic title
`cdate` / `mdate`	`YYYY-MM-DD`. Today unless user says else
`tags`	1–5 lowercase keywords

TEMPLATES — scenario back

Markdown

---
version: 1
name: { Topic }
cdate: { YYYY-MM-DD }
mdate: { YYYY-MM-DD }
tags: [{ tag1 }, { tag2 }]
---

## Front

**Concept:** {1–3 sentences}

## Use case

{2–4 sentences}

## Back

**Example:** {prose}

**Takeaway:** {one line}

MDX

<Memo
  version={1}
  name="{Topic}"
  cdate="{YYYY-MM-DD}"
  mdate="{YYYY-MM-DD}"
  tags={["{tag1}", "{tag2}"]}
>
  <Front>

**Concept:** {1–3 sentences}

  </Front>

## Use case

{2–4 sentences}

  <Back>

**Example:** {prose}

**Takeaway:** {one line}

  </Back>
</Memo>

HTML

<article
  class="memo"
  data-version="1"
  data-name="{Topic}"
  data-cdate="{YYYY-MM-DD}"
  data-mdate="{YYYY-MM-DD}"
  data-tags="{tag1},{tag2}"
>
  <section class="front">
    <p><strong>Concept:</strong> {1–3 sentences}</p>
  </section>
  <section class="use-case">
    <h2>Use case</h2>
    <p>{2–4 sentences}</p>
  </section>
  <section class="back">
    <p><strong>Example:</strong> {prose}</p>
    <p><strong>Takeaway:</strong> {one line}</p>
  </section>
</article>

TEMPLATES — code back

Markdown

## Back

**Example:**

```{lang}
{snippet}
```

{1–2 sentences}

**Takeaway:** {one line}

MDX

  <Back>

**Example:**

```{lang}
{snippet}
```

{1–2 sentences}

**Takeaway:** {one line}

  </Back>

HTML

<section class="back">
  <p><strong>Example:</strong></p>
  <pre><code class="language-{lang}">{snippet}</code></pre>
  <p>{1–2 sentences}</p>
  <p><strong>Takeaway:</strong> {one line}</p>
</section>

RULES

Front: clear concept. MDX → inside <Front>. HTML → .front. Markdown → ## Front
Use case: when/who/why. Not feature list. Not same as Back example
Back: show don't restate concept. Takeaway ≠ Concept
Batch: one memo block each, blank line between, same format throughout
Style: short sentences. Accurate > clever

EXAMPLES

→ references/examples.md