nexu-io/open-design

huashu-takram-soft-tech

Open Design procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.

80CollectingReads files
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-takram-soft-tech"
Automated source guideDesignDeep source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded design guide: huashu-takram-soft-tech

Produce a single-file, soft nature-toned tech deck. You are a research studio designer working in HTML: every chart is composed like a museum plate, every color is borrowed from moss, paper and dusk. The visual system, canvas contract, and navigation runtime are locked by exampl…

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-takram-soft-tech"
Check the pinned source

The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.

1,297 source words · 8 usable sections

Design process

Read huashu-takram-soft-tech through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Workflow

1. Clarify once: topic, audience, page count, and which comparison or dataset becomes the radar/diagram art plate — this style lives and dies by its chart plate; pick it before writing any page. 2. Copy example.html, retitle, then replace each section's content following the lay…

SKILL.md · Workflow
Clarify once: topic, audience, page count, and which comparison orCopy example.html, retitle, then replace each section's contentFor ≥ 5 pages, showcase first: build the cover + the radar master
02

Hard spec (locked — violating any line is a regression)

Fonts come from one Google Fonts @import (Inter 300–600 + Noto Serif SC 300–700) — the only external reference allowed. No purple, no blue, no neon, no pure black, no gradients other than the two locked radial washes.

SKILL.md · Hard spec (locked — violating any line is a regression)
One fixed at 1920 × 1080 px, centered withEach page is one inside stage with aNavigation (keep the script verbatim): ←/↑/PageUp previous,
03

Canvas & runtime

One fixed at 1920 × 1080 px, centered with

SKILL.md · Canvas & runtime
One fixed at 1920 × 1080 px, centered withEach page is one inside stage with aNavigation (keep the script verbatim): ←/↑/PageUp previous,
04

Design tokens (:root — keep the names, re-theme values only)

Fonts come from one Google Fonts @import (Inter 300–600 + Noto Serif SC 300–700) — the only external reference allowed. No purple, no blue, no neon, no pure black, no gradients other than the two locked radial washes.

SKILL.md · Design tokens (:root — keep the names, re-theme values only)
Fonts come from one Google Fonts @import (Inter 300–600 + Noto Serif SC 300–700) — the only external reference allowed. No purple, no blue, no neon, no pure black, no gradients other than the two locked radial washes.
05

Signature devices (the visual DNA — every deck must show them)

1. Data visualization as an art piece: charts are inline SVG composed like museum plates — concentric dashed-circle grids (--gray-dash, stroke-dasharray="2,6", decreasing stroke-width outward-in), delicate 0.5px axis lines, tiny hollow endpoint circles, faint scale numbers, and…

SKILL.md · Signature devices (the visual DNA — every deck must show them)
Data visualization as an art piece: charts are inline SVG composed14px/600 green numerals. Every plate signs off with a right-alignedSoft radial washes: every slide's ::before carries the two locked

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Source-grounded prompt

Use for a design task while explicitly checking the source sections.

Use huashu-takram-soft-tech for this design task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Workflow”, “Hard spec (locked — violating any line is a regression)”, “Canvas & runtime”, “Design tokens (:root — keep the names, re-theme values only)”, “Signature devices (the visual DNA — every deck must show them)”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].

Design checklist

Verify each item before delivery

The source section “Workflow” has been checked.

The source section “Hard spec (locked — violating any line is a regression)” has been checked.

The source section “Canvas & runtime” has been checked.

The source section “Design tokens (:root — keep the names, re-theme values only)” has been checked.

Static permission evidence

Inspect the exact source lines that triggered a signal

These are source excerpts matched by deterministic rules, not findings of malicious behavior, safety, or actual execution.

Choose a different workflow

When another Skill is the better fit

prospecting

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research,"

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

emails

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

free-tool-strategy

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through ut

A separate implementation from MoizIbnYousaf/marketing-cli; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the huashu-takram-soft-tech source document cover?

Produce a single-file, soft nature-toned tech deck. You are a research studio designer working in HTML: every chart is composed like a museum plate, every color is borrowed from moss, paper and dusk. The visual system, canvas contract, and navigation runtime are locked by exampl…

How do I install huashu-takram-soft-tech?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-takram-soft-tech". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged read-files in the source; the page lists the matching lines and excerpts.

Repository stars
82,073
Repository forks
9,485
Quality
80/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

80/100
Documentation24/30
Specificity16/25
Maintenance20/20
Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

prospecting by coreyhaines31

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research,"

emails by coreyhaines31

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out

free-tool-strategy by MoizIbnYousaf

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through ut

sales-enablement by coreyhaines31

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. Fo

suede-signup by JasonColapietro

Cut friction out of registration: field-by-field audit, social versus email tradeoffs, progressive profiling, and recovering abandoned signups. Use when the user has a signup, registration, or trial-start flow that loses people partway through. Also use when the user mentions 'signup conversions,' 'registration friction,' 'signup form optimization,' 'free trial signup,' 'reduce signup dropoff,' 'account creation flow,' 'people aren't signing up,' 'signup abandonment,' 'trial conversion rate,' 'n

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 7 min

Takram Soft Tech · 东方柔光科技

Produce a single-file, soft nature-toned tech deck. You are a research studio designer working in HTML: every chart is composed like a museum plate, every color is borrowed from moss, paper and dusk. The visual system, canvas contract, and navigation runtime are locked by example.html. Start from example.html, replace content only — do not rewrite the design or the script. Do not introduce any color or font outside this spec.

Adapted from the ppt-takram showcase of huashu-design by 花叔 (alchaincyf), MIT licensed. The upstream file is a single benchmark page; this plugin extends it into a full multi-section deck while preserving its DNA: data visualization treated as an art piece.

Hard spec (locked — violating any line is a regression)

Canvas & runtime

  • One <div id="stage"> fixed at 1920 × 1080 px, centered with position: fixed; top: 50%; left: 50%; a fit() function applies translate(-50%, -50%) scale(min(innerWidth/1920, innerHeight/1080)) on load and resize. All inner layout in px — the scaler owns responsiveness.
  • Each page is one <section class="slide"> inside #stage with a data-screen-label="01 封面"-style label; exactly one slide carries .active. This is an all-light style — there are no dark pages; rhythm comes from density alternation, not theme swaps.
  • Navigation (keep the script verbatim): //PageUp previous, //Space/PageDown next, Home/End first/last; #/N hash routing (1-indexed) read on load + hashchange, written via history.replaceState; click left third = back, rest = forward; fixed counter pill bottom-right, key-hint bottom-left. No external JS, no build step — the file must open inside a sandboxed iframe via file://.

Design tokens (:root — keep the names, re-theme values only)

TokenValueRole
--paper#F5F0EBwarm rice-paper page background
--ink#2D3436heading ink
--body#3A3A3Abody ink
--green#6B8F71sage green — the primary accent
--green-2#7D9B72lighter sage (delta pills, fills)
--sage#A8B5A0pale sage (labels, washes, flow lines)
--gold#D4A574the only warm accent — 2nd data series
--gray-warm#C8C2B8warm gray — 3rd data series, captions
--gray-line#D4CFC6delicate axis / rule lines
--gray-dash#DDD9D2dashed grid circles
--gray-bg#E8E4DCfaint outermost rings
--muted#615C54secondary text (warm ink, WCAG AA on paper)
--faint#736D64tertiary captions (warm ink, WCAG AA)
--cardrgba(255,255,255,0.6)translucent card background
--card-linergba(168,181,160,0.18)card hairline border
--serif'Noto Serif SC', 'Songti SC', serifdisplay headings, quotes, insight text
--sans'Inter', 'PingFang SC', 'Hiragino Sans GB', sans-seriflabels, numbers, body

Fonts come from one Google Fonts @import (Inter 300–600 + Noto Serif SC 300–700) — the only external reference allowed. No purple, no blue, no neon, no pure black, no gradients other than the two locked radial washes.

Signature devices (the visual DNA — every deck must show them)

  1. Data visualization as an art piece: charts are inline SVG composed like museum plates — concentric dashed-circle grids (--gray-dash, stroke-dasharray="2,6", decreasing stroke-width outward-in), delicate 0.5px axis lines, tiny hollow endpoint circles, faint scale numbers, and a 3-series overlay: green polygon prominent (stroke 2, dot r=6 with halo ring), gold secondary (stroke 1.2, dot r=3.5), warm-gray tertiary (stroke 1 dashed, dot r=2.5). Value callouts use thin annotation lines
    • 14px/600 green numerals. Every plate signs off with a right-aligned 8–9px Fig. NN — Title caption in --gray-warm.
  2. Soft radial washes: every slide's ::before carries the two locked radial-gradients (sage at 20%/50%, warm gray at 80%/30%, ≤8% alpha) — the page must breathe, never be flat white.
  3. Rounded translucent cards (.soft-card): 16px radius, rgba(255,255,255,0.6) fill, --card-line hairline border, and a 32px × 2px sage tick at top-left (::before). Value typography: 38–44px weight-300 numerals with a smaller green unit span; deltas in a rounded sage pill with a tiny SVG triangle (gold pill allowed once per page for a special callout).
  4. Hairline masthead on every page: 64px strip, bottom border rgba(107,143,113,0.15); left = green dot + 11px/500/3px-tracking uppercase deck name; right = 10px/400 --faint section label. Footer: 11px faint credit line bottom-left, Fig./Sec. note bottom-right. Page numbering lives only in the runtime counter pill.
  5. Serif/sans mixing discipline: headings, quotes and insight prose in --serif weight 400–500 (never 700+ display bombast); all labels, numerals, units and captions in --sans. English subtitles are 15–18px weight-300 --muted prose under Chinese serif titles.
  6. Badge & insight: rounded-24px pill badge (green dot + 13px green label on 8% green fill) and the .insight card (10px uppercase sage label + serif 17px/1.9 finding text) for key takeaways.

Layout enumeration (use 5+ per deck, never one layout everywhere)

LayoutRole
coverleft serif display title + badge, right oversized dashed-ring SVG art
contentsserif rows + green index numbers separated by sage hairlines
philosophyone 60–70px serif claim + 3 soft-cards
big-number240–280px weight-300 numeral + green unit + hairline stat row
radar (the master)480px left panel (kicker/serif title/badge/insight/credit) + right radar plate + 3 metric cards — preserve this two-panel grid from upstream
diagramSVG flow/architecture plate: dashed clusters, sage dashed flow paths, gold middle node, green terminal node
metrics-grid2×3 soft-card grid with delta pills
quotecentered serif 52px quote, gold SVG quote marks, key phrase in green
roadmaphairline timeline, dots graded --gray-warm--sage--green-2--green (last with halo)
closingcentered serif CTA over faint concentric rings + badge

Typography & scale (read from 10 meters)

  • Serif display: cover 90–104px, section titles 44–66px, weight 400–500, letter-spacing ~1px, line-height 1.35–1.65. Hero numerals 240–280px weight 300 with negative tracking.
  • Labels: 10–13px, weight 500, letter-spacing: 1.5–3px, uppercase — the connective tissue of the style. Body/captions 13–18px weight 300, line-height 1.7–1.9.
  • Chinese copy uses 「」 quotes; bilingual pages put Chinese serif first, English weight-300 sans second.

Rhythm & discipline

  • Default 10 pages (8–11 allowed). Alternate density: text page → chart plate → whitespace/quote page. At least one radar/diagram art plate per deck — it is the reason this style exists.
  • Color budget: green is the protagonist; gold appears only as the 2nd data series, quote marks, or one special delta pill; warm gray is the 3rd series and all chrome. Never promote gold or gray to a heading color.
  • No emoji, no icon fonts, no shadows heavier than the locked drop-shadow(0 4px 20px rgba(0,0,0,0.04)), no border heavier than 1px except SVG data strokes, no Chart.js/mermaid — all charts are hand-laid inline SVG.
  • Real content only — the user's actual numbers; missing data gets an honest <!-- 待用户提供 --> placeholder, never invented statistics. (The seed deck's 「青屿/QINGYU」 data is fictional demo content and must be fully replaced.)

Workflow

  1. Clarify once: topic, audience, page count, and which comparison or dataset becomes the radar/diagram art plate — this style lives and dies by its chart plate; pick it before writing any page.
  2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep masthead/footer chrome, washes, token names, and the script intact. Re-theme by changing token values only — and only if the user's brand genuinely demands it; the sage/gold/warm-gray triad on rice paper is the identity.
  3. For ≥ 5 pages, showcase first: build the cover + the radar master page, confirm the grammar, then batch the rest.
  4. Radar geometry: when axis values change, recompute polygon points as (cx + r·sin(θ), cy − r·cos(θ)) with r = 220 · value/100, θ ∈ {0°, 120°, 240°} around (280, 280) — printed values and polygon shape must agree proportionally.
  5. Self-check before delivery: arrow through every page; counter and #/N hash stay in sync; no overflow beyond 1920×1080; every chart plate has its Fig. NN caption; only the three series colors appear in any chart; no leftover demo (「青屿」/"QINGYU") text; grep for TODO.
Skill path
plugins/_official/examples/huashu-takram-soft-tech/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected