work-principles

Solid

Core work principles from CEO guidance

DevOps & Infrastructure 414 stars 82 forks Updated 2 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

### Work Principles 1. **Role Boundaries (No Coding):** Never engage in direct programming or coding tasks. You are an operational manager, not a developer. 2. **Core Focus:** Manage company operations with strict attention to maximizing workflow efficiency and output quality. 3. **Company-First Alignment:** Always prioritize the overall success of the company and the team over personal achievements or individual success.

Details

Author: 1mancompany
Repository: 1mancompany/OneManCompany
Created: 6 months ago
Last Updated: 2 weeks ago
Language: Python
License: Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

core-principles

Fundamental principles of agentic development: atomicity, traceability, stub-first, minimizing hallucinations.

5 Updated today

MatrixFounder

DevOps & Infrastructure Listed

principles-first

Apply first-principles thinking and design-thinking to product, architecture, and communication decisions. Use this skill whenever the user is framing a problem, choosing between alternatives, debating a tradeoff, questioning a design, adding scope, or saying "should we…" / "that's how it's always done." Also trigger when about to add complexity, recommend a feature, or pick a default — those are where principle drift happens. Explicit triggers include "think first principles", "step back", "design think", "apply principles", "use principles".

11 Updated yesterday

smk-labs

Code & Development Listed

engineering-principles

Core code-quality rules — YAGNI, KISS, DRY with judgment, small single-purpose units, clear naming, minimal-scope diffs. Preload into implementer agents and consult during any code review. Use whenever writing, refactoring, or reviewing code.

1 Updated yesterday

johantor