Accept issues, avoid one or two word explanations for questions ("Cool", "Syntax", etc.), replace the "hack" text in the source with a "TODO" or something, use more thoughtful variable names, make a good case for using this syntax over the available alternatives, and make good commit messages.
If this was part of your portfolio and I was looking to hire you, I would definitely have you in the "maybe" pile (instead of the "yes" pile) because of the apparent lack of skill in documentation, communication, and sympathy for your fellow devs. I would hate to work at a company that supported this style of presentation.
You went through the trouble of creating a test file, but it's empty :(
Aside from that, I think the syntax looks good!