> For the complete documentation index, see [llms.txt](https://docs.ni-ka.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ni-ka.fun/brand/brand-guideliness.md).

# Brand Guideliness

This page outlines the official visual identity, colors, typography, and interface layout constraints for **NI-KA**. Any community content, promotional media, or custom layouts should follow these guidelines to keep the game's signature webtoon arcade look.

***

## 📐 1. Skew Angles & Interface Shapes

NI-KA's interface uses slanted, dynamic shapes mimicking comic panels:

* **Skew Angle:** Core buttons, badge tags, alerts, and hud containers must be slanted at a **10-degree angle** (`transform: skewX(-10deg)` or `skewX(-5deg)`).
* **Thick Borders:** Textures and buttons use bold, black borders (`border: 3px solid #000;`) to create a hand-drawn cartoon outline look.

***

## 🔤 2. Typography & Font Styling

* **Primary Headings & Action Text:** **Bangers** (from Google Fonts).
  * *Styling:* Bold uppercase letters, with a black outline and dropped offset shadow.
  * *CSS Reference:*

    ```css
    font-family: 'Bangers', cursive;
    -webkit-text-stroke: 1.5px #000;
    text-shadow: 2px 2px 0px #000;
    ```
* **Secondary HUD & Numbers:** **Chakra Petch** or modern clean sans-serif.
  * *Use Cases:* Currency balances, speeds, ranks, and leaderboard times.

***

## 🎨 3. Color Palettes

NI-KA uses saturated, high-contrast neon accents laid over deep dark backgrounds:

### Core Ranks & System Colors

* **PLEB / Guest Yellow:** `#ffcc00` (Vibrant yellow)
* **LAD Blue:** `#369AE8` (Sky blue)
* **CHAD Orange-Red:** `#ff4500` (Intense vermillion)
* **System Toxic Green:** `#00FF66` / `#39FF14` (Shop buttons and active highlights)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ni-ka.fun/brand/brand-guideliness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.