line-creators-market
LINE Creators Market
Reference for creating, submitting, and selling LINE stickers, emoji, and themes on Creators Market.
Do not answer LINE Creators Market specs or policy questions from memory — platform rules update frequently. Always consult the references below.
Workflow
Character Design Consultation
- Clarify user goals: sticker / emoji / theme? Target market?
- Load references/style-guide.md to match style direction
- Reference references/experts.md for successful case studies
- Check references/sticker-specs.md for technical feasibility
- Use output templates to provide structured proposals
Technical Spec Queries
- Load references/sticker-specs.md
- Answer specific spec questions, citing official data
- Flag common spec mistakes
Market Strategy Planning
- Confirm target market (Japan / Taiwan / Thailand / Global)
- Load references/market-tips.md for market-specific playbook
- Combine with references/experts.md success stories
- Provide concrete, actionable plans
Submission & Review
- Load references/creators-market-guide.md
- Guide user through the submission process
- Run quality checklist for final confirmation
Creative Framework
Before starting creation, clarify three key questions:
1. Character Positioning
- Emotional connection: What emotion or personality does the character represent? Healing, funny, sarcastic, cute?
- Usage context: In what chat scenarios would users reach for this sticker?
- Memorability: One feature that makes the character memorable (round face, distinctive eyes, signature pose)
2. Market Positioning
- Target market: Japan (healing), Taiwan (local slang), Thailand (humor), Global (universal expressions)
- Competitive analysis: Strengths and weaknesses of similar stickers? How to differentiate?
- Pricing strategy: Paid vs free (ad-supported, promotional)
3. Series Planning
- Extensibility: Can the character support multiple sticker sets? Is there a storyline?
- Character family: Can supporting characters or a world be developed?
- Cross-media: Potential for animation, merchandise licensing?
Output Templates
Character Proposal Format
Character Name:
Core Personality: (one-sentence description)
Visual Features: (appearance, color palette, signature pose)
Target Audience:
Target Market:
Usage Scenarios: (top 3-5 chat situations where users would use this)
Differentiation: (what sets it apart from existing competitors)
Extension Potential: (series expansion, cross-media possibilities)
Sticker Set Planning Format
Type: Sticker / Emoji / Theme
Quantity:
Essential Expressions: (greeting, thanks, apology, OK, NG...)
Signature Expressions: (character-specific poses, catchphrases)
Recommended Price:
Launch Timing:
Quality Checklist
- Character is clearly recognizable at thumbnail size (96x74 px)
- Expression variety covers common chat scenarios
- All image dimensions are even numbers
- File sizes within limits (sticker < 1MB, animated < 1MB, emoji < 1MB, animated emoji < 300KB)
- Background fully transparent with ~10px margin on all sides
- No copyrighted elements (brand logos, other creators' characters)
- No ads, announcements, or dates embedded in images
- Title and description are compelling and SEO-friendly
- Multi-language descriptions are accurate (title <= 40 chars, description <= 160 chars)
- Tags set (max 9 per sticker/emoji) for auto-suggest functionality
- AI usage declaration accurately set if AI was used in creation
- Previewed in simulator for chat room appearance
Reference Index
| File | Topic |
|---|---|
| sticker-specs.md | Full technical specs for stickers, animated stickers, emoji, and themes |
| style-guide.md | Five creative style guides and design principles |
| experts.md | Top global creator database and success strategies |
| market-tips.md | Market-specific playbooks, pricing, SEO, and promotion |
| creators-market-guide.md | Creators Market platform operations, review rules, and revenue model |
| theme-specs.md | Theme design best practices, color coordination, readability tips |
Language-Aware Links
All Creators Market URLs use https://creator.line.me/{lang}/.... Match {lang} to the user's language (see creators-market-guide.md for the full mapping). Default to en if uncertain.
Tools
- LINE Sticker Maker: iOS | Android | Info — mobile sticker creation from photos/videos
- Sticker Simulator: Preview stickers in chat room context before submission (in Creators Market web dashboard)
- Photoshop Template: Official PSD template for theme creation (CS6+)
- LINE STORE Search: LINE Sticker Maker — browse existing LINE Sticker Maker creations
More from abgne/line-dev
messaging-api
Comprehensive reference for LINE Messaging API — webhook setup, message sending, Flex Message design, Rich Menu management, audience targeting, insights, coupons, and channel access tokens. This skill should be used when the user asks to "build a LINE Bot", "set up a webhook", "send a push message", "design a Flex Message", "create a Rich Menu", "manage audience targeting", "get messaging insights", "create a coupon campaign", "debug webhook signature verification", or mentions LINE Messaging API, LINE OA chatbot, reply/push/multicast/narrowcast/broadcast, Flex Message JSON, Rich Menu, group chat bot, channel access token, or URL schemes. Always use this skill whenever the user mentions LINE bots, chatbots, LINE OA, or any messaging-related LINE integration, even if they don't explicitly say "Messaging API".
47line-liff
Comprehensive reference for LINE Front-end Framework (LIFF) SDK — building web apps inside LINE with authentication, messaging, QR scanning, permanent links, pluggable SDK, and LIFF plugin development. This skill should be used when the user asks to "build a LIFF app", "initialize liff.init()", "send messages from LIFF", "use Share Target Picker", "scan a QR code in LIFF", "create a permanent link", "develop a LIFF plugin", or mentions LIFF SDK, LINE Front-end Framework, CDN/npm integration, pluggable SDK tree-shaking, LIFF-to-LIFF transitions, LIFF browser vs external browser, Endpoint URL configuration, or server-side ID token verification from LIFF. Always use this skill whenever the user mentions LIFF, web apps inside LINE, or LINE Front-end Framework, even if they don't explicitly say "LIFF SDK".
39line-login
Comprehensive reference for LINE Login (OAuth 2.1) — authorization code flow, PKCE, token management, ID token JWT verification, user profiles, bot linking, and login button design. This skill should be used when the user asks to "implement LINE Login", "add Log in with LINE", "set up OAuth authorization flow", "verify an ID token", "refresh an access token", "link a bot to login", "design a login button", or mentions LINE Login, OAuth 2.1, PKCE, authorization code flow, ID token JWT verification, token refresh/revocation, user profile retrieval, bot linking, SSO login, LIFF authentication, or LINE MINI App authentication. Always use this skill whenever the user mentions LINE authentication, social login with LINE, or OAuth flows involving LINE, even if they don't explicitly say "LINE Login".
27line-notification-message
Reference for LINE Notification Messages — phone-number-based messaging to non-friends, template type (premade layouts) and flexible type (custom Flex Message), delivery completion webhooks, user consent flow, SMS authentication, and billing. Use when the user asks to "send a notification message via phone number", "hash a phone number for PNP", "handle delivery completion webhook", "set up template or flexible notification", "check notification message count", "integrate LON", or mentions LINE notification messages, LINE Official Notification (LON), PNP push, phone-number-based delivery, hashed phone number, notification template, delivery completion event, consent states, or SMS authentication for notifications. Always use this skill whenever the user mentions LINE notification messages, PNP, LON, LINE Official Notification, LINE 通知型訊息, or phone-based LINE messaging to non-friends, even if they don't explicitly say "notification message".
21line-mini-app
Comprehensive reference for LINE MINI App — Service Messages, Common Profile Quick Fill, In-App Purchase, Console setup (3 internal channels), submission review, and performance guidelines for web apps running inside LINE as an enhanced LIFF platform. This skill should be used when the user asks to "build a LINE MINI App", "send a service message", "set up Common Profile Quick Fill", "implement in-app purchase", "configure MINI App Console", "submit MINI App for review", or mentions LINE MINI App, Service Messages, notification token, Common Profile, IAP purchase flow, 3 internal channels, consent simplification, Custom Path, custom share messages, or verified vs unverified MINI App. Always use this skill whenever the user mentions LINE MINI App, mini apps in LINE, or enhanced LIFF features like service messages or in-app purchase, even if they don't explicitly say "MINI App".
16