Bitcoin Is Money
Official@bitcoin-is-money · France
Standardizes enterprise-grade TypeScript architecture, Angular frontend patterns, and rigorous security auditing for Bitcoin-focused financial applications.
Agent Skills by Bitcoin Is Money
Showing 6 vetted skills indexed across 1 GitHub repositories.
bitcoin-is-moneyapi-routing
Defines scalable Hono route factories with zod validation and centralized error handling.
bitcoin-is-moneydomain-modeling
Structure BIM domain logic with hexagonal architecture entities and value objects.
bitcoin-is-moneyangular-patterns
Describe and implement reusable Angular frontend patterns for BIM apps.
bitcoin-is-moneytesting-conventions
Standardize unit and integration test conventions across BIM project packages.
bitcoin-is-moneysecurity-audit
Identify and document security vulnerabilities in BIM's codebase with severity ratings.
bitcoin-is-moneyts-rules
Enforce TypeScript coding conventions for type safety and code quality.
Frequently Asked Questions About Bitcoin Is Money
FAQPage SchemaWhat specific technical tasks are enabled by these standards?▼
These standards enable the implementation of robust Hono route factories, centralized error handling, and strict TypeScript enforcement. They facilitate the creation of reusable Angular frontend components and ensure domain logic is structured through hexagonal architecture, providing a consistent foundation for financial application development.
Which engineering personas benefit from these conventions?▼
Full-stack engineers and software architects working on financial platforms benefit from these conventions. They are designed for developers requiring high-integrity codebases, standardized testing protocols, and rigorous security auditing to maintain type safety and architectural consistency across complex, multi-package environments.
What are the primary prerequisites for implementing these patterns?▼
Implementation requires a TypeScript-based environment and familiarity with Hono for routing and Angular for frontend development. Developers must adopt the specified hexagonal architecture patterns and adhere to the defined unit and integration testing conventions to ensure full compatibility with the existing codebase structure.