If you use Claude Code or OpenCode read on... I've created a set of specialized agents and commands to make your AI coding much more effective.

GitHub

GitHub - accolver/agents: A collection of helpful agents to use with any coding system

A collection of helpful agents to use with any coding system - accolver/agents

Change from "Review my code for security issues" to "@code-reviewer review my code for security issues" to get SUBSTANTIALLY better results. One command to install a suite of helpful subagents and commands. If you find it useful, leave a star!

Intent + skills = (almost) everything Would we need encryption, contracts, etc of we could truly know a man's heart. If a promise given meant a deferred result guaranteed, then we could do away with much of the overhead of social and economic engagement. But the heart of man remains a deeply guarded enigma. Many appear like the flower, but are the snake beneath. There is still the random nature of existence that upsets the best-laid plans (hence the insurance industry), but societies could overcome much more with the ability to accurately assess intention and skill.

Larry Tesler, inventor of the cut, copy, and paste commands, dies at 74 View quoted note → View quoted note →

Men are ruled by either principles or principalities

Highly relevant given the Charlie Kirk shooting View quoted note →

"90% of problems can be solved by waiting" #nietzsche The remaining 10% by building on #nostr and #bitcoin

NIP-05 - Mapping Nostr keys to DNS-based internet identifiers In order to allow human-readable aliases to pubkeys (identities on #nostr) or proving association with a domain, #nip 05 defines the method for linking identity with web domains. The critical part is to host this file on the domain you wish to prove association (not necessarily ownership) of: /.well-known/nostr.json This JSON returns the pubkey(s) and (optionally) the preferred relays. If the pubkey returned (from the domain to which you are trying to prove association) matches the "nip05" field in a kind:0 event, then nostr clients can link the two.

NIP5 - NIP-05 - Mapping Nostr keys to DNS-based internet identifiers

Read more about the NIP5 on {{appUrl}} - NIP-05 - Mapping Nostr keys to DNS-based internet identifiers

#learning

NIP-02 - Follower Lists This #nostr #nip creates an optional kind-3 to store a list of public keys (and optional pet names) that one follows. It uses a list of "p" tags (profiles). Changes to ones follower list are complete and replace older events. This can be used for backups, discovery of related users, and human readable hierarchy of follower chains.

New goal: read a NIP every day NIP-01: Not really an "improvement" but rather the base of the whole protocol. It defines the client and the relay and the communication between them. It's a simple event based model (not dissimilar to the CloudEvents spec). It focuses on "who" (pubkey and sig) said "what" (kind and content) "when" (created_at). The "where" is loosely associated with your chosen relay. The "how" is the Nostr protocol itself. The "why" is a much more philosophical answer.

Methods are many, principles are few. A man who has mastered the principle is free to choose his method. - Emerson

Man doesn't avoid poison because it will kill him, but because it's not sweet enough - Nietzche

Life can only be understood backwards but must be lived forwards