# Hello World

Welcome to my terminal blog! This is my first post.

## About This Site

This portfolio website is built as an interactive **terminal emulator** using:

- Next.js
- React
- TypeScript
- styled-components

## Why a Terminal?

I love the command line interface. It's fast, efficient, and feels like home for developers.

### Features

1. Command history with arrow keys
2. Tab autocomplete
3. Multiple color themes
4. File system navigation

# Terminal Tips & Tricks

Here are some tips for using this terminal:

## Navigation

| Command | Description |
|---------|-------------|
| `help` | Show all available commands |
| `ls` | List files in current directory |
| `tree` | Show directory tree |
| `cat <file>` | Display file contents |
| `themes` | Check available themes |
| `language` | Switch language (en/vn) |

> Use tab completion to save time typing commands.

## Keyboard Shortcuts

- **Tab** or **Ctrl+I**: Autocomplete command
- **Up Arrow**: Previous command
- **Down Arrow**: Next command
- **Ctrl+L**: Clear terminal
- **Ctrl+U**: Clear current line

## Themes

Change the look with `themes set <name>`:

- dark
- light
- blue-matrix
- espresso
- green-goblin
- ubuntu
- nikk

## Language

Switch language with `language set <en|vn>`:

- `language set en` - English
- `language set vn` - Vietnamese

Happy hacking!


hello-world.md

# Building My Personal AI Work Assistant with Claude Code

As a Developer, I juggle multiple tools daily to manage my task: JIRA for work tracking, Taskwarrior for personal todos, and Obsidian for detailed notes. Context switching between these systems was eating into my productivity. So I built [nikk-assistant](https://github.com/ndp190/nikk-assistant), a Claude Code assistant with prebuilt commands to assist me in managing my workday.

## The Problem

My task inspecting workflow involved:
- Opening JIRA to check ticket status
- Create Taskwarrior task for quick work entry
- Create Obsidian notes if the task is complex and need a detailed write-up
- Manually inspect my work status across all systems

Each context switch costs mental energy. I needed a single entry point.

## The Solution

[nikk-assistant](https://github.com/ndp190/nikk-assistant) is a set of custom Claude Code commands that act as a bridge between my work management systems. Instead of visiting multiple tools, I interact with Claude, which orchestrates everything behind the scenes.

I just essentially one shot Claude Code with this prompt:

```markdown
Create a CLAUDE.md file at ~/.claude/CLAUDE.md for my work assistant setup.

## My Workflow

I work at Go1 as a technical/infrastructure role. My work tracking workflow:

1. **JIRA** (Atlassian) - Source of truth for all tickets. I have the Atlassian MCP connected. My team ticket is prefix with IT-[ticket-num], for example https://foo.atlassian.net/browse/IT-1234

2. **Taskwarrior** - Local CLI task manager. I use it to:
   - Track JIRA tickets locally for quick access
   - Log ad-hoc tasks that don't warrant a JIRA ticket
   - Tasks linked to JIRA should have tag format: +jira:PROJ-123
   - example task (with logs manually added by me)
    Name          Value
    ID            10
    Description   IT-1234 Clean up current AWS IAM users groups access
                    2025-11-11 08:46:34 A to review excel file
                    2025-11-20 16:08:20 Sent message for J on list of account that need to be audit
                    2025-11-21 11:42:04 TODO investigate on C client usage
    Status        Pending
    Project       Work
    Entered       2025-11-10 21:08:55 (6w)
    Last modified 2025-12-08 16:15:44 (2w)
    Virtual tags  ANNOTATED PENDING PROJECT READY UNBLOCKED
    UUID          12345678-90ab-cdef-1234-567890abcdef
    Urgency       2.252

3. **Obsidian** - Task notes at "Obsidian/Works"
   - Used as scratchpad and detailed journal for complex tasks
   - Not all tasks need an Obsidian note

## What I need from the assistant

- Generate standup reports (yesterday's work, today's plan, blockers)
- Show my todo list for the day
- Create Taskwarrior tasks from JIRA tickets
- Create ad-hoc tasks
- Generate end-of-day journals
- Weekly/sprint reports

## Include in CLAUDE.md

1. Context about my workflow and tools
2. File naming conventions for Obsidian notes
3. Taskwarrior tag conventions (especially jira linking)
4. Common Taskwarrior commands I'll need
5. Standup format template
6. My typical JIRA projects (you can search my accessible Atlassian resources to find which projects I have access to)
7. Instructions for the assistant on how to handle each type of request

First, search my Atlassian/JIRA to find:
- My JIRA projects I have access to
- My current open tickets to understand my work context

Then create a comprehensive CLAUDE.md that will help Claude Code assist me effectively with this workflow.
```

Then I created individual command files for each action I needed, testing and refining as I went.

### Key Commands

**`/standup`** - My morning routine in one command. It:
- Queries Taskwarrior for completed and pending tasks
- Fetches my recent JIRA activity
- Pulls relevant Obsidian notes
- Generates a formatted standup summary

**`/todo`** - A unified view of all my pending work across systems. In-progress items appear first, followed by to-do items, with duplicates automatically filtered out.

**`/jira <ticket>`** - Fetches ticket details including status, description, and recent comments. If I have Obsidian & Taskwarrior notes linked to the ticket, those appear too.

**`/add-task`** and **`/add-jira-task`** - Create tasks that sync across systems with proper tagging.

## Tech Stack

- **Claude Code** - The AI assistant framework, gluing everything together
- **MCP (Model Context Protocol)** - For Atlassian/JIRA integration
- **Taskwarrior** - Local CLI task management
- **Obsidian** - Note-taking

## Architecture

The project is simple:

```
nikk-assistant/
├── CLAUDE.md           # Configuration and guidelines
├── .claude/
│   ├── settings.local.json  # Permissions for MCP tools
│   └── commands/            # Custom command definitions
│       ├── standup.md
│       ├── todo.md
│       ├── jira.md
│       └── ...
```

Each command is a markdown file that defines what Claude should do when invoked. The magic happens through MCP integrations and shell commands that Claude executes.

## Results

What used to take 15-20 minutes of each day context-gathering now takes seconds. I ask Claude for my standup, it compiles everything, and I'm ready to share with my team.

The real win is cognitive load reduction. I no longer need to remember which system holds what information. Claude acts as my unified interface to all work data.

A screenshot of the `/standup` command in action:
![Standup Command Screenshot](https://r2.nikkdev.com/blog/nikk-assistant-0.jpeg)

## What can be improved

- Assist in more areas in my workflow
- Making it AI platform agnostic

If you're drowning in tools to manage your work, consider building your own assistant configuration, because Claude Code makes the process surprisingly straightforward. You can just vibe code a custom assistant tailored to your exact workflow. Fun fact: the whole building process for my AI assistant took only 30 minutes.


nikk-assistant.md

blog

terminal

The following is an update on the security vulnerability identified in December 2025.

MongoDB Server Security Update, December 2025 | MongoDB

Things We Can Learn from Claude Code Building Our Own Agents If you’ve been building AI agents, you’ve probably noticed that the most effective ones often look surprisingly simple. Claude Code …

Things We Can Learn from Claude Code | by Marco Kotrotsos | Dec, 2025 | Medium

Ditherpunk — The article I wish I had about monochrome image dithering — surma.dev

Our perception of brightness is non-linear.

There’s nothing wrong with tweaking the image when the automated algorithms make the wrong call.

What an unprocessed photo looks like: (Maurycy's blog)

A study by a Singapore government agency has found that children exposed to high levels of screen time before age two showed brain development changes linked to slower decision-making and higher anxiety in adolescence, adding to concerns about early digital exposure.

Singapore Study Links Heavy Infant Screen Time to Teen Anxiety - Bloomberg

Google is dead. Where do we go now? - Circus Scientist

A far more detailed explanation of prompt caching than anyone asked for.

Prompt caching: 10x cheaper LLM tokens, but how? | ngrok blog

Discover the inner workings of ISO 8583, the global standard for credit card transaction messaging. Learn how it powers payment processing across networks and explore its structure, fields, and real-world applications.

Terminal Portfolio