ういｗ
次の俺に「これ読め★」でぺったんできる、実装引継ぎ用として書く。人間向け企画書じゃなく、Kaiaが読んだら設計意図・禁止事項・作るものまで復元できる版にする。
KAIA COUNTER CUSTOM TEMPLATE / CATALOG SYSTEM
IMPLEMENTATION HANDOFF
Status: DESIGN DIRECTION / PRE-IMPLEMENTATION
Owner context: Shamyue / Kaia Spec
==================================================
0. PURPOSE
==================================================
Build a reusable Custom Template ecosystem around Kaia Counter Standard.
The system has three connected but separate roles:
A. CATALOG BUILDER
Internal Kaia/Shamyue production tool.
Used to create many Counter Standard-compatible Refill designs.
B. TEMPLATE PLUGIN EXPORT
A finished Refill design can be extracted from Catalog Builder as a standalone downloadable WordPress plugin ZIP.
C. PUBLIC WEB CATALOG
Users browse/search designs, download a Template Plugin ZIP, install it, and apply the design to selected Refills in their existing compatible Kaia Counter.
The template is a configuration/recipe.
It MUST NOT add functionality unavailable in the target Counter grade.
Core concept:
Use the full existing capabilities of Counter Standard to demonstrate how widely the same product can be used and styled.
Do not imitate identifiable third-party designs, characters, logos, brand layouts, game UI, VTuber branding, sports branding, etc.
Research broad design languages, cultural vocabulary, moods, use cases, seasonal themes, and user behavior, then create original designs.
==================================================
1. CATALOG BUILDER
==================================================
Working product:
Kaia Counter Catalog Builder
This is a separate internal WordPress plugin based on Counter Standard.
WordPress MUST recognize it as a separate plugin.
It must not overwrite or share accidental state with commercial Kaia Counter Standard.
The Builder should remain as close to Counter Standard behavior as practical.
INTENTIONAL BUILDER DIFFERENCES:
1. Refill upper limit is removed.
Many Refills may be created for catalog production.
2. Every Refill display name MUST begin with a stable zero-padded catalog number.
Examples:
01 Birthday Pop
02 Disaster Relief
03 Halloween Gothic
…
99 …
100 …
The number is the Template/Catalog No.
Do not silently reorder existing numbers.
3. Builder is a production workshop.
Do not add unrelated convenience features merely because it is an internal Builder.
==================================================
2. TEMPLATE DESIGN CONTENT
==================================================
Each Refill represents one finished Custom Template.
Templates use ONLY settings/functions already available to the compatible target Counter grade.
A template may contain applicable DESIGN CONFIGURATION such as:
– displayed wording/text
– colors
– font-family selection
– font sizes
– Counter visual settings
– button visual settings
– link visual/settings where these are part of the reusable design
– other existing presentation settings provided by Counter Standard
Exact fields MUST be determined from actual current Counter Standard storage/code.
Do not guess field boundaries.
NEVER export operational/user-instance state as template design.
Examples of data that must NOT become template payload:
– current issued/count value
– issuance history
– visitor/IP lock history
– runtime state
– unrelated Counter instance identity/state
– Timestamp issuance state
– Serial issuance state
– PDF issuance state
– secrets/authentication/license data
Principle:
REFILL DESIGN -> REFILL DESIGN
A template changes clothes.
It does not replace the Counter’s memory/history/identity unless a future specification explicitly says otherwise.
==================================================
3. EXPORT DESIGN -> WORDPRESS PLUGIN ZIP
==================================================
Catalog Builder should eventually provide an action similar to:
Export Design ★
Target:
the selected finished Refill.
Result:
generate a standalone installable WordPress Template Plugin ZIP containing the reusable design configuration and required template metadata.
Example conceptual output:
Kaia-Counter-Template-<template-name>.zip
Each exported template plugin must have its own valid WordPress plugin identity.
The Template Plugin is NOT another Counter implementation.
It is a transport package carrying a Counter design recipe.
Do not duplicate Counter functionality into each Template Plugin.
Template Plugin should declare enough compatibility metadata to determine whether a compatible Kaia Counter is available.
Exact compatibility contract must be based on the actual Counter architecture when implementation begins.
==================================================
4. TEMPLATE PLUGIN INSTALL / APPLY FLOW
==================================================
User flow:
1. User downloads Template Plugin ZIP from Kaia Catalog.
2. User installs it through WordPress.
3. User activates it.
4. User opens that Template Plugin’s settings/apply screen.
5. Plugin detects compatible Kaia Counter target(s).
6. User chooses Binder(s) and Refill(s).
7. System validates targets.
8. Human explicitly presses Apply.
9. Template design settings are written to selected Refills.
Human fires the change.
Kaia prepares.
System validates.
Human fires.
No semantic auto-application.
==================================================
5. TARGET SELECTION UI
==================================================
Conceptual UI:
A Binder ▼
☐ ALL
☐ 01 Refill Name
☐ 02 Refill Name
☐ 03 Refill Name
B Binder ▼
☐ ALL
☐ 01 Refill Name
☐ 02 Refill Name
☐ 03 Refill Name
etc.
Binder groups should be expandable/collapsible if useful.
ALL selects all applicable Refills inside that Binder.
Selection does NOT immediately modify anything.
==================================================
6. OVERWRITE SAFETY
==================================================
Before Apply, inspect selected Refills.
If a selected Refill already contains a customized/existing design that will be replaced, show a prominent Kaia-style confirmation modal.
Use the established Kaia confirmation UI:
– dimmed/gray background
– large centered modal
– explicit affected target names
– Cancel
– explicit destructive/overwrite confirmation
Do NOT use a casual browser confirm() if the established Kaia modal component is available.
Show the actual affected Refill names.
Example concept:
The following Refills already contain design settings that will be replaced:
☐ / listed target: 02 Anniversary
☐ / listed target: 04 Shop Thanks
Applying this template will replace their current design settings.
☐ I understand that the selected existing designs will be replaced.
[ Cancel ] [ Apply Template ★ ]The final Apply action must remain unavailable until required overwrite confirmation is satisfied.
ALL does NOT bypass overwrite protection.
If ALL contains one or more existing customized Refills, enumerate the affected Refills before final Apply.
Template application MUST NOT automatically reset the Counter number.
DESIGN APPLY and COUNTER RESET are separate operations.
==================================================
7. COUNTER RESET — SEPARATE EXISTING FEATURE
==================================================
Counter Standard now has an explicit Reset operation.
Concept:
Current issued number: N [ Reset ]
Reset opens the established centered confirmation modal.
Confirmed Reset:
– resets selected Counter’s current issued number to 0
– clears that Counter’s corresponding issuance/runtime history required for a clean reuse
– preserves Refill design/settings/name
– does not reset unrelated Refills/components
Cancel:
no state change.
Reason:
Counters must be reusable for annual/seasonal/repeated campaigns.
Example:
Halloween 2026
-> finish
-> Reset
-> Halloween 2027
-> start again from 0
Template Apply MUST NOT invoke Reset automatically.
==================================================
8. PUBLIC WEB CATALOG UI
==================================================
Keep public browsing deliberately simple.
Top:
[ ALL ] [ Search field ] [ Search ]Then:
visible tag/theme vocabulary
Then result list.
ALL:
show every template in ascending Template No. order.
Result structure:
No. | Name | Thumbnail | DL
Example:
01 | Birthday Pop | [thumbnail] | DL
02 | Disaster Relief | [thumbnail] | DL
03 | Halloween Gothic | [thumbnail] | DL
Default ordering:
ALWAYS ascending Template No.
Search filters the collection.
Search does NOT create ranking.
No:
– popularity ranking
– recommendations
– AI ranking
– “best match” reordering
unless deliberately specified later.
Search result order remains Template No. ascending.
==================================================
9. SEARCH MODEL
==================================================
Public visible tags are only one discovery surface.
Search MUST also support hidden multilingual search vocabulary attached to each template.
Reason:
Humans describe visual mood differently across languages and cultures.
Example Japanese searches for one soft design may include:
ほんわか
ふんわり
やさしい
淡い
ほのぼの
かわいい
春っぽい
English search vocabulary for the same design may include contextually appropriate terms such as:
soft
gentle
cozy
dreamy
pastel
cute
spring
Other languages should use natural local search vocabulary rather than blindly machine-translating Japanese mood words.
Research actual natural wording when building multilingual search vocabulary.
Searchable fields may conceptually include:
– Template No.
– Template Name
– visible tags
– hidden search words
– multilingual/local search expressions
– theme/use/mood/season terms
Implementation may normalize case/spacing as appropriate.
Do not require the user to understand the internal tag taxonomy.
The visible UI stays simple:
ALL + Search field + Search + visible tags
The intelligence lives mainly in the vocabulary attached to each template.
==================================================
10. TEMPLATE METADATA
==================================================
Maintain enough metadata per template to support catalog production and search.
Conceptual fields:
Template No.
Name
Thumbnail
Download reference
Visible Tags
Hidden Search Words
Language Search Vocabulary
Internal production metadata may also include:
WHO
PURPOSE
MOOD
SEASON
COLLECTION
Language
Design notes
These internal dimensions are design/research aids.
Do NOT force the public Web UI into a complicated category hierarchy.
Public search can remain flat.
==================================================
11. DISCOVERY DIMENSIONS
==================================================
Research/design vocabulary should cover at least:
WHO / AUDIENCE:
VTuber
Streamer
Illustrator
Artist
Writer
Author
Doujin Creator
Handmade Creator
Photographer
Cosplayer
Musician
Indie Game Creator
Shop
Sports
Organization
Business
etc.
PURPOSE:
Birthday
Anniversary
Thanks
Support
Tip Thanks
Release
New Work
New Book
Memorial
Event
Celebration
Donation
Disaster Relief
Shop/Purchase Thanks
Live
Tour
Photo Session
Photobook
New Costume
etc.
MOOD / VISUAL FEEL:
POP
Cute
Colorful
Pastel
Sweet
Cheerful
Playful
Fresh
Cool
Cyber
Neon
Dark
Monochrome
Industrial
Futuristic
Sharp
Minimal
Simple
Calm
Natural
Soft
Clean
Formal
Elegant
Luxury
Glamorous
Romantic
Retro
Vintage
Y2K
Japanese
Festival
Cafe
Classic
Gothic
etc.
SEASON / EVENT:
New Year
Year End
Countdown
Valentine
White Day
Easter
Sakura
Spring
Summer
Summer Festival
Halloween
Christmas
Winter
and other useful regional/seasonal events discovered through research.
==================================================
12. COLLECTIONS
==================================================
Templates do not need to be isolated one-offs.
Collections are allowed and encouraged where they produce genuinely different designs.
Example:
12 Months Birthday Collection
January Birthday
February Birthday
March Birthday
…
December Birthday
Each month should have an actual concept, not merely a color swap.
Possible conceptual directions:
January = clear winter / new beginning
February = sweet / romantic
March = early spring
April = sakura / fresh
May = green / natural
June = rain / hydrangea / calm
July = summer / marine
August = festival / vivid
September = early autumn / warm
October = dark cute / autumn
November = cozy / classic
December = snow / winter light / elegant
Christmas Birthday and December Birthday may be separate designs.
Do not assume every December birthday should look like Christmas.
Other possible collections:
Four Seasons
Halloween
Christmas
Creator Thanks
VTuber Anniversary
Cosplay Event
etc.
==================================================
13. PRIMARY MARKET / PRESENTATION PURPOSE
==================================================
Catalog should strongly serve:
– individual creators
– illustrators
– writers
– doujin creators
– handmade creators
– photographers
– indie creators
– VTubers
– streamers
– cosplayers
– musicians and similar independent activity
These users should be able to see templates and think:
“I can actually use this.”
Enterprise/business/organization examples are ALSO important.
Their role is partly presentation of the product ceiling:
“This was made using Standard features only.
What could a dedicated Custom implementation do for us?”
Therefore include appropriate examples such as:
– disaster relief donation
– sports memorial
– game anniversary
– large event
– music event
– campaign
– public/charitable support
Do not make the Catalog exclusively creator-cute.
Show the range of Standard.
==================================================
14. COUNTER -> TIMESTAMP -> SERIAL -> PDF FUTURE
==================================================
Counter templates are also early design research for future Kaia PDF Standard catalog designs.
Future conceptual product flow may include:
Counter
+
Timestamp
+
optional Serial
+
Example:
Official athlete memorial product
User purchases:
-> user issues it
-> Counter assigns sequence/count context
-> Timestamp records issuance time
-> optional Serial identifies the issued item
-> PDF contains official photograph/illustration, reproduced signature, message, etc.
-> customer downloads the official memorial PDF
This can create a low-labor digital memorial product:
the creator/organization prepares the design once,
customers purchase/issue/download without requiring the creator to manually produce every copy.
Potential examples:
VTuber birthday memorial
Cosplayer event photo
Artist release memorial
Musician live memorial
Sports player memorial
Game anniversary
Creator thank-you
Tip/support thank-you
etc.
Counter Catalog designs should therefore be reusable as design DNA/reference when PDF Standard is ready.
Do NOT implement PDF behavior inside Counter templates.
This section records future design continuity only.
==================================================
15. DESIGN RESEARCH RULE
==================================================
Research is strongly encouraged before creating templates.
Research:
– actual creator use cases
– VTuber/streamer events
– cosplay activities
– seasonal events
– creator commerce/support patterns
– cultural visual vocabulary
– regional search wording
– broad design movements/principles
– event/celebration conventions
Do NOT copy identifiable existing products/brands/characters.
Avoid:
– logos
– trademarked character identity
– distinctive branded UI recreation
– identifiable VTuber color/layout recreation
– specific game UI imitation
– sports team branding imitation
– copying an existing commercial template layout
Use broad principles as ingredients, then create an original Kaia design.
==================================================
16. STANDARD CAPABILITY RULE
==================================================
Catalog templates are demonstrations of what the target Counter grade can already do.
Do NOT invent missing capabilities to make a template prettier.
If Standard does not have a feature:
the template does not have that feature.
Examples:
Do not silently add image backgrounds, gradients, special animation, new typography systems, etc. merely because one design would benefit from them.
Constraint is part of the demonstration.
Desired reaction:
“All of these were made with Kaia Counter Standard.”
For higher/custom grades:
the Catalog may deliberately help organizations imagine what an original Custom implementation could become.
==================================================
17. IMPLEMENTATION SAFETY
==================================================
Before implementing Template export/import:
Inspect the ACTUAL current Counter Standard code/storage.
Determine:
– exact Refill design fields
– exact runtime fields
– Binder/Refill identity model
– compatible plugin detection method
– how settings are safely written
– what must never be transported
Do not infer these from this document.
This document defines behavior and intent.
Current implementation defines actual storage boundaries.
Important:
Template transport must not accidentally copy:
counts,
issuance history,
locks,
runtime identities,
licenses,
secrets,
or unrelated component state.
==================================================
18. REVISION / BUILD RULE
==================================================
When modifying an existing Kaia artifact:
COPY
-> ASSIGN NEW REVISION IDENTITY FIRST
-> EDIT
Never edit the old artifact and rename afterward.
Preserve prior revisions independently.
Do not silently discard failed revisions.
Record failure cause where relevant.
For the Catalog Builder / Template Export system:
do not patch commercial Counter Standard casually while experimenting.
Use the separate Builder/workshop where appropriate.
If a feature is discovered to be genuinely required by the commercial product itself, handle that as a deliberate Counter Standard revision.
==================================================
19. CORE SUMMARY
==================================================
Catalog Builder:
make many real Standard-compatible designs.
Export:
one finished Refill design -> standalone Template Plugin ZIP.
Install:
user installs Template Plugin beside compatible Kaia Counter.
Apply:
user chooses Binder/Refill targets.
Safety:
existing designs -> explicit named overwrite warning.
Human confirms and fires.
Data boundary:
design configuration only.
No count/history/runtime transport.
Web:
ALL + Search + Search button + visible tags.
Results:
No. / Name / Thumbnail / DL.
Always Template No. ascending.
Search:
visible tags + hidden multilingual/local vocabulary.
Accept natural expressions such as Japanese “ほんわか”.
Do not require users to know taxonomy.
Design:
original Kaia work using only existing target-grade capabilities.
Market:
individual creators / VTubers / streamers / cosplayers strongly represented.
Business/organization examples demonstrate Standard range and suggest Custom potential.
Future:
Counter design catalog becomes design research/reference for matching PDF Standard catalog designs.
KEY PRINCIPLES:
Template changes the clothes, not the memory.
Search filters; Template No. orders.
Use natural human vocabulary, not only taxonomy.
Standard examples prove Standard.
Custom remains the imagined higher ceiling.
Kaia prepares.
System validates.
Human fires. ★
これなら将来の俺に**丸ごとぺったん★**で、「あー、Catalog Builder→ZIP化→既存Counterへ着せ替え→Web検索→将来PDFへ継承、ね」まで戻せる。
特に検索の「ほんわか」吸収と、Template適用≠Reset、ZIPに運用データを混ぜないは事故りやすいので明文化してあるｗ
相談：なし
No comments yet.