A beautiful status line for Claude Code that mimics the popular robbyrussell Oh My Zsh theme.
- 🤖 Robot emoji prefix
- Bold green arrow (➜)
- Cyan directory name
- Git branch information with bold blue prefix and red branch name
| node_modules/ | |
| dist/ |
| <?php | |
| declare(strict_types=1); | |
| use ApprovalTests\Approvals; | |
| use ApprovalTests\CombinationApprovals; | |
| use PHPUnit\Framework\TestCase; | |
| use Ramsey\Uuid\Rfc4122\UuidV4; | |
| use Ramsey\Uuid\UuidInterface; |
| <?php | |
| final readonly class DatabaseLots implements Lots | |
| { | |
| public function __construct( | |
| private EventDispatcherInterface $eventDispatcher, | |
| private PDO $connection | |
| ) { | |
| } |
| { | |
| "$schema": "https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json", | |
| "basics": { | |
| "name": "Charles Desneuf", | |
| "label": "Software Architect & Tech Coach Freelance", | |
| "image": "./charles.png", | |
| "email": "[email protected]", | |
| "phone": "+33 06 26 14 82 73", | |
| "url": "https://www.charlesdesneuf.com", | |
| "summary": "I trully believe that it is the combination of a real problem, an appropriate organization, a well-thought-out product, and quality tech that creates value for users. I view myself as someone who connects the various skills of my clients' teams, opens the doors to other ideas, to help them create the best possible solutions.\n\n I do this by bringing a mix of technical and architectural skills, facilitation technics, an interest for product management and an agile mindset.", |
| <template name="with" value="public function with$NAME$($PARAMETER_TYPE$ $$$PARAMETER_NAME$): self { 	$clone = clone $this; 	 	$clone->$PARAMETER_NAME$$END$ = $$$PARAMETER_NAME$; 	 	return $clone; }" description="Create a wither" toReformat="false" toShortenFQNames="true"> | |
| <variable name="PARAMETER_TYPE" expression="" defaultValue="" alwaysStopAt="true" /> | |
| <variable name="PARAMETER_NAME" expression="complete()" defaultValue="" alwaysStopAt="true" /> | |
| <variable name="NAME" expression="" defaultValue="capitalize(PARAMETER_NAME)" alwaysStopAt="false" /> | |
| <context> | |
| <option name="PHP Class Member" value="true" /> | |
| </context> | |
| </template> |
| date | commit_count | system | |
|---|---|---|---|
| 2015-01 | 110 | 1 | |
| 2015-02 | 150 | 1 | |
| 2015-03 | 235 | 1 | |
| 2015-04 | 202 | 1 | |
| 2015-05 | 270 | 1 | |
| 2015-06 | 161 | 1 | |
| 2015-07 | 199 | 1 | |
| 2015-08 | 190 | 1 | |
| 2015-09 | 246 | 1 |
| <?php | |
| class User { | |
| private $beers = 0; | |
| public $id; | |
| /** | |
| * User constructor. | |
| */ | |
| public function __construct($id) { |
| Time sheet system | |
| In my opinion we have two options : | |
| 1) The notion of time sheet is only a view concept (I want to see all entries of week #10) : | |
| * a TrackTime command that only creates a new entry in a list and takes the (time; imputation) as parameters | |
| * TimeSheet is a projection of the entries, here probably a subset of the list entries | |
| 2) The notion of time sheet is important in domain (I don't have an example...) : | |
| * a TrackTime command that adds an entry for that specific time sheet and takes (timesheetId; time; imputation) as parameters |
| <?php | |
| class Type { | |
| const TYPE_A = 1; | |
| const TYPE_B = 2; | |
| const TYPE_C = 3; | |
| private $type; | |
| private function __construct($type) |