Category
Sports discovery, booking, open-play coordination, and venue operations for cities in the Philippines.
Brand system · agent-readable
Aktib is the transaction and coordination layer for real-world sports: discovery, booking, open play, venue operations, community, and safe handoffs.
Warm operational surfaces, energetic sport accents, and grounded trust cues. Never generic fitness hype. Never cold enterprise software.
Aktib should feel like organized momentum: reliable enough for payments and venues, warm enough for friends and communities, and energetic enough for people who actually play.
Sports discovery, booking, open-play coordination, and venue operations for cities in the Philippines.
Players, venue owners, coaches, clubs, sports communities, and business partners who need trust without friction.
A living city court grid: slots, people, movement, handoffs, and play signals coming into order.
Not a generic social app. Not just venue listings. Aktib owns the moment where plans become confirmed play.
Less chasing. More playing. Users feel oriented, invited, and confident that the slot, group, or handoff is real.
Clear state, confirmed ownership, visible rules, human support, and safe payment/provider foundations.
Use warm paper and deep forest as the base. Lime is an energetic action accent, not a full-page background. Clay, gold, aqua, and rose are sport/community accents used sparingly.
Use clear, direct copy. Keep paragraphs short. Explain status, trust, and action without hype.
PHP 840 · 4 live now · AKTIB-PAY-001Aktib copy should be direct, warm, concrete, and status-aware. Prefer verbs that describe real actions: book, join, confirm, transfer, review, list, seed, verify.
Use the same brand ingredients across social posts, presentations, emails, PDFs, invoices, admin dashboards, and app screens. The system should flex by format without changing personality.
These rules keep outputs consistent when different agents create different assets.
Lead with the real event, city, sport, or venue. Use large type, one image or texture, and one action. Avoid busy collages.
Use editorial title slides, compact operational tables, and one strong number per slide. Keep chart colors tied to the token palette.
Warm paper background, white/paper cards, forest CTA, concise body, clear fallback links, no large image dependency.
Use lane or court-grid metaphors. Show state transitions and actor responsibilities. Keep labels short.
Prioritize legibility, totals, due dates, references, and support details. Use brand color only for headers and key totals.
Dense, calm, and task-focused. Avoid oversized heroes, decorative cards, and marketing copy inside operational workflows.
The JSON below is the source block agents should parse when creating assets. Keep it synced when the brand changes.