💡 Remember Box

how to clarify your purpose

- find the pain you can sustain
- locate your unfair cognitive advantage
- use purpose to kill options (reduce entropy)
- A/B test your life

12 views17:26

💡 Remember Box

it's more like having a filter than deciding convincingly at once

13 views17:28

💡 Remember Box

how to clarify your purpose - find the pain you can sustain - locate your unfair cognitive advantage - use purpose to kill options (reduce entropy) - A/B test your life

pain I can sustain

- hard technical work with uncertainty
- high-ambiguity reasoning
- long arcs of problem-solving without external validation
- learning new stacks fast and applying them immediately

unfair cognitive advantage

- pattern detection + cross-domain synthesis
- fast prototyping instinct
- early signal sensitivity

13 views17:30

💡 Remember Box

my purpose is to make the frontier usable

13 views17:31

💡 Remember Box

💡 Remember Box pinned «my purpose is to make the frontier usable»

17:31

💡 Remember Box

or in other words, to find overlooked edges and build tools that make the future arrive early

13 views17:31

💡 Remember Box

for me, the real point of AGI was to understand myself better and more

13 views17:52

💡 Remember Box

https://github.com/supertone-inc/supertonic

13 views18:14

💡 Remember Box

> Build workflows
> Monetize every run with x402
> Turn them into a product
> Tokenize it

12 views04:25

💡 Remember Box

claude opus 4.5 is superhuman at coding tasks

12 views06:03

💡 Remember Box

prompts I use often

- make a comprehensive analysis of current state of the app which and check api also, then improve each and every part and route of it, as it was mostly build earlier by an intern and we can't know if it all works, also consider each section and workflow then add unit tests for each as well and refactor it overall, improve UI/UX too

- improve entire app UI, check where it can be improved to make the UX super good

- make small commits and push

- resolve merge conflicts

- review everything and improve if there's something you can

12 viewsedited 08:35

💡 Remember Box

[2507.13334] A Survey of Context Engineering for Large Language Models
https://arxiv.org/abs/2507.13334

arXiv.org

A Survey of Context Engineering for Large Language Models

The performance of Large Language Models (LLMs) is fundamentally determined by the contextual information provided during inference. This survey introduces Context Engineering, a formal discipline...

12 views11:18

💡 Remember Box

Forwarded from Adrian Galilea

Create ~/.claude/commands/commit.md or whatever is the windows equivalent:


---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
denied-tools: Bash(git add -A:*), Bash(git add -A), Bash(git add --all:*), Bash(git add --all)
description: Create a git commit
---

## Context

- Current git status: !`git status`
- Staged changes: !`git diff --cached`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

## Your task

Create a single git commit following these rules:

1. **NEVER use `git add -A` or `git add --all`** - This is explicitly forbidden and blocked by permissions.
2. **Check for staged files** - "Changes to be committed" commit ONLY those files. They were deliberately staged.
3. Follow the commit message style from recent commits shown above